One advantage of sqlite is that migrations work much better than postgres, so it is great to use while developing your app.
On Sep 11, 4:14 am, Joe Barnhart <[email protected]> wrote: > Good point. Another factor is handling threads. IIRC Sqlite won't handle > more than 1 thread while the others will. > > On Thu, Sep 10, 2009 at 8:01 AM, ctalley <[email protected]> wrote: > > > FYI, something to consider is that SQLite doesn't natively support > > foreign key constraints. For example, ON DELETE CASCADE doesn't > > work. It is possible to write triggers to handle referential > > integrity, but a dbms like postgresql just does it. So, depending on > > your requirements, postgresql might be a better option for that > > reason. > > >http://www.sqlite.org/cvstrac/wiki?p=ForeignKeyTriggers > > > On Sep 9, 12:16 pm, greenpoise <[email protected]> wrote: > > > Is it a good alternative? I am a fan of Postgresql myself BUT just for > > > the simplicity of the whole development, can SQLite handle the job in > > > the long run (users, record, db size)? I am sure is almost transparent > > > when using both (correct me if I am wrong) but doesnt the Auth method > > > changes? > > > > Feedback greatly appreciated. > > > > Dan > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
