jararaca wrote:
>
>
> Thanks Russ, I don't have a stray settings-file but I've spotted the
> problem now: One of my files with custom SQL for the models contained
> the line USE xy; (with xy being my database, argh!). So everything
> before the execution of this line used my test database correctly but
> all later commands were executed on the real database.
>
> Happy testing to all of you,
> micha
>
>> > But the strangest part is yet to come: When testing, it is obviously
>> > always my "real" database that is being read, not the 'test_xy'
>> > database, even if I change DATABASE_NAME in settings!
>
>
> --~--~---------~--~----~------------~-------~--~----~
> 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
> -~----------~----~----~----~------~----~------~--~---
>
>
>
Hi jararaca
Can u brief me the solution.Even i am not able to access test
database ,some how it fetch production database itself
regards,
//g
--
View this message in context:
http://old.nabble.com/unit-tests%3A-database-confusion-tp10737510p28536896.html
Sent from the django-users mailing list archive at Nabble.com.
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
