Revision history  [back]

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSetting values for those accounts that you have created programmatically.values.

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts #will create an initial revision
python manage.py fix_answer_counts #fixes incorrect answer counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations where data becomes corrupted by rolling back transactions that had an uncaught exception. (With postgres you'll also get relevancy ranking on full text search and automatically "and"ed search. In mysql search is "od"ed and is not very specific). In MySQL at the moment you have to choose between support of transactions and the full text search capability.

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSetting values.

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts #will create an initial revision
python manage.py fix_answer_counts #fixes incorrect answer counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations where data becomes corrupted by rolling back transactions that had an uncaught exception. (With postgres you'll also get relevancy ranking on full text search and automatically "and"ed search. In mysql search is "od"ed and is not very specific). In MySQL at the moment you have to choose between support of transactions and the full text search capability.specific)

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSetting values.

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts #will create an initial revision
python manage.py fix_answer_counts #fixes incorrect answer counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations where data becomes corrupted by rolling back transactions that had an uncaught exception. corrupted. (With postgres you'll also get relevancy ranking on full text search and automatically "and"ed search. In mysql search is "od"ed and is not very specific)

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSetting values.

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts #will create an initial revision
fix_revisionless_posts
python manage.py fix_answer_counts #fixes incorrect answer counts
fix_answer_counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations where data becomes corrupted. (With postgres you'll also get relevancy ranking on full text search and automatically "and"ed search. In mysql search is "od"ed and is not very specific)

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSetting values.

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts
python manage.py fix_answer_counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations where data becomes corrupted. (With postgres you'll also get relevancy ranking on full text search and automatically "and"ed search. In mysql search is "od"ed and is not very specific)with corrupted data.

Something muste be out of hand. I've seen this problem on an installation where the program was trowing an exception between the time question is saved and the revision is intended to be saved.

The exception was SMTPError, but in your case it could be something else, like for example some people missing EmailFeedSettingEmailFeedSettings values..

There are management commands that "bandaid" that and related issues, but to really fix this we need to find what throws the exception and why.

python manage.py fix_revisionless_posts
python manage.py fix_answer_counts

You can also try postgres and the database backend. With postgres django will run every request in its own transaction and will help prevent situations with corrupted data.