johm/freeskool — comment on commit 4807130d7d38b2ea4e594c54d7b1f292ff8278d9
File: db/migrate/20120202125718_create_sessions.rb line 5
By johm:

it's a simplifying assumption for the algorithm that will test to see if
a course can be scheduled at a given time. you can grab everything on
the date, and then look at the time, rather than having to run really
complicated tests across date ranges which sql won't be good at.

so no multi day events, but that's fine, because we have a session
repetition concept baked into the course model pretty deeply anyway.

On 2/16/12 3:13 PM, Jason Lewis wrote:
> Just curious - what's the purpose for having a date as well as the start and end times?
>
> I don't think ActiveRecord / ActiveSupport support having detached 'time' types - the time is always married to a date, IIRC. could possibly remove session_date and change the following columns to :start_time and :end_time. Would allow for multi-day events, if those ever happen, as well.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/johm/freeskool/commit/4807130d7d38b2ea4e594c54d7b1f292ff8278d9#commitcomment-975096