On Fri, Dec 11, 2009 at 2:39 PM, Nikolas Everett <nik9...@gmail.com> wrote: > > > On Fri, Dec 11, 2009 at 3:50 PM, Joshua D. Drake <j...@commandprompt.com> > wrote: >> >> On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote: >> > Turning fsync off on a dev database is a bad idea? Sure you might >> > kill it and have to start over, but thats kind of the point in a dev >> > database. >> >> My experience is that bad dev practices turn into bad production >> practices, whether intentionally or not. > > Fair enough. I'm of the opinion that developers need to have their unit > tests run fast. If they aren't fast then your just not going to test as > much as you should. If your unit tests *have* to createdb then you have to > do whatever you have to do to get it fast. It'd probably be better if unit > tests don't create databases or alter tables at all though.
This is my big issue. dropping / creating databases for unit tests is overkill. Running any DDL at all for a unit test seems wrong to me too. Insert a row if you need it, MAYBE. Unit tests should work with a test database that HAS the structure and database already in place. What happens if your unit tests get lose in production and drop a database, or a table. Not good. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
