Note that the database is stored in just a few files, which are pretty easy to track down. So turn database server off, copy the files, turn database on, run your test, turn database off, restore the files with the copies. And turn database on again.
If you insist on a "freeze" solution, I would consider reverting with LVM snapshots on a special partition. With sufficient RAM, the copy-on-write sectors may reside on a RAM disk, so you get very good performance, and you can wipe the changes right away. Hope this helps, Eli Shmuel Fomberg wrote: > hi all. > > at work we have a test suit that run against a database. so in the > beginning of the test it populate the database with a predefined data. > the problem is that this process is way too long, making the test suit > take a long time to run. > so I'm looking for options to cut this time. > > is there any ability to freeze a database? so all the changes will be > temporary and disappear in the end of the test, leaving the database in > a clean state for the next test? > maybe some kind of middleware? > maybe using transactions? (mysql supports transactions, right?) > can transaction hold a large amount of operations / data? (I don't want > to limit the test of what it can do to the data...) > > Shmuel. > _______________________________________________ > Perl mailing list > [email protected] > http://mail.perl.org.il/mailman/listinfo/perl > > > -- Web: http://www.billauer.co.il _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
