Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add computed columns, move properties #167

Open
jjeising opened this issue Apr 25, 2018 · 0 comments
Open

Add computed columns, move properties #167

jjeising opened this issue Apr 25, 2018 · 0 comments

Comments

@jjeising
Copy link
Member

A while ago we already planed to move some commonly (in the tracker) used properties to columns in tbl_ticket. A first guidance would probably be

public static function with_default_properties(Model_Resource $resource) {
self::with_properties($resource, [
'Fahrplan.DateTime' => 'fahrplan_datetime',
'Fahrplan.Day' => 'fahrplan_day',
'Fahrplan.Room' => 'fahrplan_room'
]);
}

While moving code like this it may also be a good idea to add computed columns for ticket properties depending on the encoding profile. The encoding profile of a ticket and the properties of a ticket (e.g. if depends on other tickets) rarely change but lot's of joins are required to fetch related properties.

We should also define a convention for computed columns (like _is_master).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant