component: database | priority: major | keywords: database, refactoring
2015-10-04 13:27:19: @a-tze created the issue
Following properties should be (re-)introduced as real database fields:
Fahrplan.ID
Fahrplan.Start (or Fahrplan.DateTime)
Fahrplan.Duration
Fahrplan.Room
Fahrplan.Day (?)
Fahrplan.GUID
Fahrplan.Title
This will add complexity to the application, because these need to be remapped into Properties here and there, but the framework for that is already there, because it is already done. The gain will be performance (should be tested before).
Another alternative to the remapping of properties, maybe including virtual properties: store them duplicated in database and sync with triggers. Property changes are rare, but the mentioned fields are read very often, and often used for JOINS.
Issue migrated from trac ticket # 115
component: database | priority: major | keywords: database, refactoring
2015-10-04 13:27:19: @a-tze created the issue
Following properties should be (re-)introduced as real database fields:
Fahrplan.DurationThis will add complexity to the application, because these need to be remapped into Properties here and there, but the framework for that is already there, because it is already done. The gain will be performance (should be tested before).
Another alternative to the remapping of properties, maybe including virtual properties: store them duplicated in database and sync with triggers. Property changes are rare, but the mentioned fields are read very often, and often used for JOINS.