Author: jacob Date: 2008-09-03 18:10:07 -0500 (Wed, 03 Sep 2008) New Revision: 8959
Modified: django/trunk/docs/ref/databases.txt django/trunk/docs/releases/1.0.txt Log: Added the last notes about 1.0, including the inevitable (short!) list of known issues. Modified: django/trunk/docs/ref/databases.txt =================================================================== --- django/trunk/docs/ref/databases.txt 2008-09-03 22:46:39 UTC (rev 8958) +++ django/trunk/docs/ref/databases.txt 2008-09-03 23:10:07 UTC (rev 8959) @@ -13,6 +13,8 @@ usage. Of course, it is not intended as a replacement for server-specific documentation or reference manuals. +.. _mysql-notes: + MySQL notes =========== @@ -240,7 +242,6 @@ .. _sqlite-notes: - SQLite notes ============ Modified: django/trunk/docs/releases/1.0.txt =================================================================== --- django/trunk/docs/releases/1.0.txt 2008-09-03 22:46:39 UTC (rev 8958) +++ django/trunk/docs/releases/1.0.txt 2008-09-03 23:10:07 UTC (rev 8959) @@ -212,7 +212,37 @@ replaced by the dispatcher, file-uploading and file-storage refactorings introduced in the Django 1.0 alpha releases. -Thanks -====== +Known issues +============ -So many people. Really. \ No newline at end of file +We've done our best to make Django 1.0 as solid as possible, but unfortunately +there are a couple of issues that we know about in the release. + +Multi-table model inheritance with ``to_field`` +----------------------------------------------- + +If you're using :ref:`multiple table model inheritance +<multi-table-inheritance>`, be aware of this caveat: child models using a custom +``parent_link`` and ``to_field`` will cause database integrity errors. A set of +models like the following are **not valid**:: + + class Parent(models.Model): + name = models.CharField(max_length=10) + other_value = models.IntegerField(unique=True) + + class Child(Parent): + father = models.OneToOneField(Parent, primary_key=True, to_field="other_value", parent_link=True) + value = models.IntegerField() + +This bug will be fixed in the next release of Django. + +Caveats with support of certain databases +----------------------------------------- + +Django attempts to support as many features as possible on all database +backends. However, not all database backends are alike, and in particular many of the supported database differ greatly from version to version. It's a good idea to checkout our :ref:`notes on supported database <ref-databases>`: + + - :ref:`mysql-notes` + - :ref:`sqlite-notes` + - :ref:`oracle-notes` + --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
