Ask Your Question

Best practices to avoid data inconsistency

asked 2011-03-09 21:16:01 -0500

psyklic gravatar image

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.

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2011-03-09 22:17:45 -0500

Evgeny gravatar image

updated 2011-03-09 22:53:16 -0500

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.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2011-03-09 21:16:01 -0500

Seen: 1,012 times

Last updated: Mar 09 '11