FYI, this has some known issues with the way unittesting works. It basically boils down to the fact that sqlite memory dbs do not write until commit which means that if you insert several row of data and then try to query them you will get an error from sqlite that the data "does not exists". Gustavo and Mark did a great job working around this (at the expense of slower tests execution) and it's all out only in tg2.0b7. So please upgrade!
On Thu, Mar 12, 2009 at 9:33 AM, dazza <[email protected]> wrote: > It should be possible to tell SQLite to use a 'memory database'. In TG1.x > you set > > Â sqlalchemy.dburi = "sqlite:///:memory:" > > in the cfg file. > > On Thu, Mar 12, 2009 at 1:17 PM, Artem Marchenko <[email protected]> > wrote: >> >> Hi >> >> Is there a possibility to use in-memory database in TG2? >> I have quite many DB-related tests in my app that currently uses >> SQLite. I would like to speed it up by not using hard drive at all. Is >> it possible? >> >> Thanks. >> Artem. >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
