First time here? Check out the FAQ!

Best practices to avoid data inconsistency

I was wondering, how do I best prevent data inconsistency errors? As far as I can tell, I haven't been doing anything crazy. Yet, already two inconsistency problems have occurred. (see

My additional problem was where my superuser suddenly could not view any questions+replies without an internal server error ... It turned out that I had to confirm his email subscription settings (manually -- the add_missing_subscriptions management command did not work; perhaps there is a bug where it does not address superusers or the original user?).

Thank you again for your help so far! If you have any best practices to avoid inconsistency errors I would be grateful.

psyklic's avatar
asked 2011-03-09 21:16:01 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


The one thing I suggest - use PostgresQL (there are other posts here explaining why). Regarding your superuser - maybe it was the one that was created by django when you initialized the project?

At the moment the installation protocol asks you to not create the superuser at that time, but add it separately (there is a special management command for that add_admin).

But if it is something else - please post more details from the error logs, such errors (of type "Internal Server Error") will be fixed very quickly.

Evgeny's avatar
updated 2011-03-09 22:53:16 -0500, answered 2011-03-09 22:17:45 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments