Re: Error migrating using South

OK, my suggestion in this case is to enable logging at the database level, since your system is down anyway. That way you can at least see what statement it's crashing on. On 6/12/12 4:29 PM, Daniel França wrote: More information: I'd put a break point just before the crash then I've tested

Re: Error migrating using South

from django.db import connection, DatabaseError try: .. except DatabaseError: connection._rollback() On Wed, Jun 13, 2012 at 5:49 PM, Daniel França wrote: > I recreated the database and still get the same error when executing a > simple "syncdb". > > Tried to

Re: Error migrating using South

I recreated the database and still get the same error when executing a simple "syncdb". Tried to change the database connection to sqlite and now I got the error that the sqlite3 module isn't installed... I think my installation is messed up. On Tue, Jun 12, 2012 at 7:29 PM, Daniel França

Re: Error migrating using South

More information: I'd put a break point just before the crash then I've tested some database queries... and all of them crash with the error: DatabaseError: current transaction is aborted, commands ignored until end of transaction block* But if I access the database using psql it's working

Re: Error migrating using South

Thanks for the anwser I've installed Haystack, and it was working fine local, but at the server I got this error. First I've tried to install haystack like I did local, using pip pip install -e git+ https://github.com/toastdriven/django-haystack.git@master#egg=django-haystack But at the server I

Re: Error migrating using South

You've got a database error lurking somewhere. I usually encounter this when syncdb needs to be run (to whit, ./manage.py syncdb). Have you added anything to installed apps that is not managed with South? If that's a dead end, see if you can enable SQL logging in the database (in

Error migrating using South

Hi all, I'm using South and it was working fine, but suddenly I start to get this error on the server that's driving me crazy: *(virtualenv)[root@localhost]# ./manage.py migrate accounts* *Traceback (most recent call last):* * File "./manage.py", line 35, in * *execute_manager(settings)* *