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
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 change the database connecti
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 w
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 f
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 g
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 PostgreSQL,
6 matches
Mail list logo
