Re: unit testing and not creating database for read only database

created http://code.djangoproject.com/ticket/14296 On Sep 16, 4:22 pm, keith wrote: > I have the same problem, have you logged a ticket for this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...

Re: unit testing and not creating database for read only database

I have the same problem, have you logged a ticket for this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr.

Re: unit testing and not creating database for read only database

Any suggestions? On Jul 7, 2:21 pm, thusjanthan wrote: > Hi, > > So I have a read only database called "information" which has been > modeled in the django framework with the managed=false for the META on > all its tables. When I run unit tests on another app I do not want the > unit tests to go

unit testing and not creating database for read only database

Hi, So I have a read only database called "information" which has been modeled in the django framework with the managed=false for the META on all its tables. When I run unit tests on another app I do not want the unit tests to go and create a test database for "information" but would rather like t