"JM" <[EMAIL PROTECTED]> writes: > The problem might be the same than the one that causes the > inserts/updates into sqlite to be incredibly slow. To be honest, I do > not understand why TurboGears sets SO+Sqlite as defaults, as it clearly > doesn't work.
It is easier to test. And to provide a quickstart. It is not recommended anywhere for production code, even though it is enough for a lot of things. I have a concept-project that I used to demo the final project to the client with 720K rows, summing up more than 80MB of SQLite-database. It works. I use PostgreSQL for production code, though, since it is much more robust and resourceful than the alternatives. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
