Hi,
Today I enforced strange situation, hope it is strange only for me nad
you will quickly tell me what stupidness I am doing.
Well, today I have switched from sqlite to postgre. Everything was
perfect since I've tried to run set of unit tests for my project.
Every time my tests deals with situation where IntegrityError is
expected test execution is stopped with error:
Error: Database test_my_project couldn't be flushed. Possible reasons:
* The database isn't running or isn't configured correctly.
* At least one of the expected database tables doesn't exist.
* The SQL was invalid.
Hint: Look at the output of 'django-admin.py sqlflush'. That's the
SQL this command wasn't able to ru
The full error: current transaction is aborted, commands ignored
until end of transaction block
When I look into postgre logs I can see that db tried to do operation
that I was expected. I don't know why with sqlite IntegrityErrors
where raised normally and with postgre thet are not.
Can't wait to hear your opinions.
Luke
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
