On 11/26/2011 01:23 AM, Gelonida N wrote: > It seems I'm not the first one who wans to run django tests with > postgressql and who doesn't have permissions to create databases. > > I found two suggestions on the web: > > One is to use sqlite for testing instead of postgres. > However I'm not really happy with this solution, as sqlite is less > sensitive to sloppyness in the code. I encountered already some issues > only with postgres, but not with sqlite. > > The other suggestion, that I found is implementing a custom test runner, > that adapts setup_databases() > > I'll probably try that approach, but was curious about other potential > tricks. >
For the time being I just followed a third path, which is requesting create privileges. I could still imagine, that it would be a good idea for some users, if the default test runner were able handle situations where one has no create database privileges. -- 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.
