Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

MyTimetable 2.4 is currently in the state: stable. No further development is expected except for critical bug fixes. MyTimetable 2.4 is tracked using the git branch: rb-2.4.

MyTimetable 2.4 focussed on redesigning the database backend in order to be able to use multiple databases at the same time and implement a new backend provider to show activities retrieved from a custom database table.

All work involved in upgrading to the latest MyTimetable version (configuration, building, testing) is free of charge for our customers with a Software Assurance support agreement.

Functional changes

  • Multiple database support and 'continuous calendar' — MyTimetable will be able to read from multiple databases at the same time, and will be able to transparently combine these databases. The user will only have to choose the appropriate database when adding a new timetable subscription.
  • Custom activity support — A new backend type will be added that gives customers the ability to add custom activities that will be retrieved from a custom database table. All-day activities will also be supported.
  • Support for all-days and multi-day events
  • Replaced department filter by posdepartment filter by default — Due to this, filtering of module and studentset listings will better match the expected behaviour; modules/student sets in search results now should match either the department directly, or the department through their pos (formerly the latter scenario was not included, leading to missing results when filtering on both pos and student set).
  • Equipment timetables
  • Refactored Syllabus Plus activity type support
  • Added link to help page on "no subscriptions" tooltip
  • Combine locations using avoid concurrency
  • Help page improvements
  • Many other small improvements and bug fixes, involving the API, exception handling, rendering and other components. In total 254 (non-merge) commits were done since version 2.3.

Non-functional, technical and back-end changes

The following changes have been made to the MyTimetable backend and underlying software, and have no direct impact on MyTimetable functionality:

  • Proper indexes and foreign keys have been added to the user preferences database. The SQL database schema will be automatically upgraded on first start of the application and any existing subscriptions will be automatically deduplicated. Since this upgrade may take some time, it may be necessary to temporarily remove or increase the socketTimeout value in the user preferences database connection string.
  • Option added to set the transactional isolation level, using the server-side property TransactionIsolation, see the Spring documentation for possible values. The default is ISOLATION_DEFAULT.
  • Carriage returns without linefeeds are now filtered when retrieving data from Syllabus Plus. These characters often end up in S+ data, for example when copying from Microsoft Excel, but cause issues when publishing iCalendar feeds.
  • Database serialisation improvements have been made, to ensure a consistent user database and prevent exceptions during concurrent access.

Removed and deprecated features

The following features from earlier MyTimetable versions have been deprecated, removed, or partially removed and are not supported anymore:

  • Internet Explorer 7

 

 

  • No labels