Tom Barrett

Current problem: We have a CSS rule ``` #body table.service-program td small, .service-details-inline small { color: #aaa !important; font-size: 75%; line-height: 0.5em; } ``` but because `small` is an inline...

This query is taking about 10 seconds for a system with lots of services.

I think the temp table is inevitable when group-by and distinct is in the mix. But we might need to find a way to avoid joining on to so many...

Hitting again. Large temp table sometimes runs into disk space issues. See also #718

The current limit is one service *per congregation* per day. Do you guys have several services on one day for the same congregation?

Further thinking on this: It's fairly coincidental that currently each service has to belong to one *congregation*. Wanting to do rosters/run sheets for things that aren't actually congregations leads us...

(As part of the upgrade, each congregation with a meeting_time set would have a corresponding event_type created). (An extra step here could be to rename "services" as "events" to express...

> I would add to that to associate roster views to event types as - for instance - I don't want to see the the Sunday service dates for play...

Notes to self about the work required to introduce a "service type" entity: - congregation_service_component table would become service_type_service_component - roster_role.congregationid would become roster_role.service_typeid - roster_role_service_field.congregationid would become roster_role_service_field.service_typeid -...

Good discussion here. Jethro doesn't currently provide good reporting on this kind of activity recorded in notes. Related issue: #728