On Mon, Jul 13, 2009 at 10:38 AM, Shawn Milochik <shawn.m...@gmail.com>wrote:
> <snip> > > > I highly highly recommend that you separate your development, testing, > and production instances of your DB and web server. You should never > ever develop or test on a production system! > > - -- > Randy Barlow > > <snip> > That's already the case. I guess I wasn't clear enough. All the tests will > only be run in the development environment, never on the test server. > > I guess I've been too stuck in the mindset that development and production > systems should be as identical as possible, and just making my Django db > login a postgres admin in test can't hurt > anything. I just didn't want to make that user a postgres admin on the > production server, and now I realize that there's nothing forcing me to do so. > > Thanks, > Shawn > > > > If you set your DATABASE_ENGINE to be sqlite3 and leave TEST_DATABASE_NAME blank it will automatically use an in memory sqlite db. The best way to do this would be to just maintain 2 settings files, with one of them inheriting the defaults from the other by means of an import *. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
