| 215 | | Thanks |
|---|
| 216 | | ====== |
|---|
| 217 | | |
|---|
| 218 | | So many people. Really. |
|---|
| | 215 | Known issues |
|---|
| | 216 | ============ |
|---|
| | 217 | |
|---|
| | 218 | We've done our best to make Django 1.0 as solid as possible, but unfortunately |
|---|
| | 219 | there are a couple of issues that we know about in the release. |
|---|
| | 220 | |
|---|
| | 221 | Multi-table model inheritance with ``to_field`` |
|---|
| | 222 | ----------------------------------------------- |
|---|
| | 223 | |
|---|
| | 224 | If you're using :ref:`multiple table model inheritance |
|---|
| | 225 | <multi-table-inheritance>`, be aware of this caveat: child models using a custom |
|---|
| | 226 | ``parent_link`` and ``to_field`` will cause database integrity errors. A set of |
|---|
| | 227 | models like the following are **not valid**:: |
|---|
| | 228 | |
|---|
| | 229 | class Parent(models.Model): |
|---|
| | 230 | name = models.CharField(max_length=10) |
|---|
| | 231 | other_value = models.IntegerField(unique=True) |
|---|
| | 232 | |
|---|
| | 233 | class Child(Parent): |
|---|
| | 234 | father = models.OneToOneField(Parent, primary_key=True, to_field="other_value", parent_link=True) |
|---|
| | 235 | value = models.IntegerField() |
|---|
| | 236 | |
|---|
| | 237 | This bug will be fixed in the next release of Django. |
|---|
| | 238 | |
|---|
| | 239 | Caveats with support of certain databases |
|---|
| | 240 | ----------------------------------------- |
|---|
| | 241 | |
|---|
| | 242 | Django attempts to support as many features as possible on all database |
|---|
| | 243 | 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>`: |
|---|
| | 244 | |
|---|
| | 245 | - :ref:`mysql-notes` |
|---|
| | 246 | - :ref:`sqlite-notes` |
|---|
| | 247 | - :ref:`oracle-notes` |
|---|
| | 248 | |
|---|
