mirror of https://github.com/django/django.git
Added the last notes about 1.0, including the inevitable (short!) list of known issues.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8959 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
96a417f91d
commit
58fad7f9fd
|
@ -13,6 +13,8 @@ This file describes some of the features that might be relevant to Django
|
||||||
usage. Of course, it is not intended as a replacement for server-specific
|
usage. Of course, it is not intended as a replacement for server-specific
|
||||||
documentation or reference manuals.
|
documentation or reference manuals.
|
||||||
|
|
||||||
|
.. _mysql-notes:
|
||||||
|
|
||||||
MySQL notes
|
MySQL notes
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
@ -240,7 +242,6 @@ matter unless you're printing out the field values and are expecting to see
|
||||||
|
|
||||||
.. _sqlite-notes:
|
.. _sqlite-notes:
|
||||||
|
|
||||||
|
|
||||||
SQLite notes
|
SQLite notes
|
||||||
============
|
============
|
||||||
|
|
||||||
|
|
|
@ -212,7 +212,37 @@ replaced by ``ModelForm``) and a number of deprecated features which were
|
||||||
replaced by the dispatcher, file-uploading and file-storage refactorings
|
replaced by the dispatcher, file-uploading and file-storage refactorings
|
||||||
introduced in the Django 1.0 alpha releases.
|
introduced in the Django 1.0 alpha releases.
|
||||||
|
|
||||||
Thanks
|
Known issues
|
||||||
======
|
============
|
||||||
|
|
||||||
|
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`
|
||||||
|
|
||||||
So many people. Really.
|
|
Loading…
Reference in New Issue