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

Yeah, I may have been over/underthinking
it....http://www.depesz.com/2007/11/21/find-overlapping-time-ranges/

On 2/17/12 3:34 PM, Jason Lewis wrote:
> Ugh... Handling the date/time stuff in this way is really making Rails tetchy... I was building the event calendar on a separate branch, but it's not going to work without some weird magics recalculating the dates for every session.... and then any efficiency we gained in the DB will be lost in the app logic. It's going to make any type of time-based querying very upset too... we should discuss alternatives at some point.
>
> What are you planning on using for the backend in production? Postgres handles date/time based queries really, really well in my experience; also, scalability is probably a YAGNI feature for this application.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/johm/freeskool/commit/4807130d7d38b2ea4e594c54d7b1f292ff8278d9#commitcomment-979692