On May 20, 5:05 am, Marco Mariani <[email protected]> wrote:
> Since there are triggers, and integrity constraints must be tested > too, I decided early in the life of the project that ROLLBACK was not > enough, but I made it work with a previous release of TG. > If I remember correctly, switching from ROLLBACK to TRUNCATE slowed > tests by about 3x I like the idea of using a truncate statement with all my tables to wipe out all the rows and then reloading them. I don't know how to use a rollback with controller tests because cherrypy (or TG) seems to issue a commit at the end of each page rendering. Can you post some of the code you're using to do this truncate and reload? Thanks Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
