[Locomotive-users] SQLite3 db is "locked" issue

[Scott Tamosunas]

It's a bad idea for your development database to be different that
your production... you are just asking for trouble. It's worth the
time to get familiar with whatever database you plan on running in
production. Prototyping is one thing but development for production
should be using as close as production as possible.

On 3/5/07, Ira Cary Blanco <blanco at samsontech.com> wrote:
> Agreed, Sqlite is very convenient for the dev environment. I wouldn't be so
> quick to write it off.
>
>
> -------------------------
> Ira Cary Blanco
> Marketing & Media
> Samson Technologies Corp.
>
>
> on 3/5/07 4:04 PM, Niko Dittmann at ni-di at web.de wrote:
>
> > Do you still have the problem when defining the timeout?  It's here
> > in the changeset (http://dev.rubyonrails.org/changeset/5258) and
> > _should_ make things really better.  I think sqlite is so convinient
> > for development that I would give it a try.  I guess, I'd even define
> > another session store for development and not sacrify the
> > convinience.  But perhaps that's just me.
> >
> >
> > Niko.
> >
> >
>
>
> _______________________________________________
> Locomotive-users mailing list
> Locomotive-users at lists.raaum.org
> http://lists.raaum.org/mailman/listinfo/locomotive-users
>