xrymbos/nztrain-v2 — comment on commit fde356ae57afdb6b8e746bd5a95bfaec04b2f224
File:  line 0
By ronalchn:

Fixed for SQLite now. Views are not a problem. Almost all SQL databases
support them. Just that SQLite doesn't support the DateTime datatype nor
the DISTINCT ON (fields) construct. Also used RANK() ON (PARTITION ...)
which is available in postgreSQL to automatically rank scores.

Latest commits working around them, either with a slightly weird query, or
some ruby calculations. Note db:migrate has different queries depending on
if SQLite or other SQL database.

If you ran db:migrate on SQLite run before, you might want to run "rake
db:migrate:redo STEP=5" to re-do a query change I made to cast
string-formatted pseudo-date datatypes into integers before performing
arithmetic on them.

If you haven't pulled changes for about a day and you're on postgreSQL,
please run "rake db:migrate" when you git pull.

Ronald

On Tue, Jan 17, 2012 at 11:17 PM, Kitten <
reply@reply.github.com
> wrote:

> also fuck yes to boris' comment
>
> On Tue, Jan 17, 2012 at 9:08 PM, Boris Pfahringer <
> reply@reply.github.com
> > wrote:
>
> > Jamie,
> > keeping it generic is useful for local development. Setting up Postgres
> is
> > a pain.
> >
> > Boris
> >
> > On 17/01/2012, at 22:55, xrymbos wrote:
> >
> > > We've already moved to postgres, SQLite was slow as balls. Is it worth
> > the effort keeping this general in case we want to move away from
> postgres?
> > >
> > > ---
> > > Reply to this email directly or view it on GitHub:
> > >
> >
> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873649
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> >
> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873671
> >
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873711
>