https://docs.befair.it/ 2026-05-02T02:57:51+00:00 https://docs.befair.it/ https://docs.befair.it/lib/exe/fetch.php?media=wiki:dokuwiki.svg text/html 2015-04-09T12:44:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.befair.it/doku.php?id=django:django-reversion&rev=1428583464&do=diff DJANGO-REVERSION Low-level API Please refer to django-reversion low level API v 1.8 It is valid for lower versions too. Switch from "django-pro-history" to "django-reversion" The steps to follow are: * delete fields django-pro-history fields from the models, where they are present; text/html 2015-02-13T11:41:36+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.befair.it/doku.php?id=django:internals&rev=1423827696&do=diff Django Internals model.Create() If you did want to create or update an object, the .save() method already has this behaviour by default, from the docs: " Django abstracts the need to use INSERT or UPDATE SQL statements. Specifically, when you call save(), Django follows this algorithm: text/html 2015-04-19T13:55:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.befair.it/doku.php?id=django:ticket_24662&rev=1429451712&do=diff My experience on trying to fix #24662 Django issue ticket dashboard Steps As a newbie of Django bug fixing, I had to understand how the bug fixing workflow works. First thing to do is to build the environment. It is good to work on a virtualenv, since the most important thing is to reproduce the bug in the exact (or more similar) environment the submitter detected the bug. Virtualenvs allow to leave the system untouched while keeping several different environments active in it.