#27629: Inconsistent check of allow_relation in
ForwardManyToOneDescriptor.__set__
-------------------------------------+-------------------------------------
Reporter: Sven Coenye | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: allow_relation | Triage Stage: Accepted
ForwardManyToOneDescriptor |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Comment:
That code hasn't changed since multiple database support was introduced in
Django 1.2 (1b3dc8ad9a28486542f766ff93318aa6b4f5999b) but you may be
correct -- at least no tests are failing with the proposed change so
that's a good sign.
I was going to make the claim that that code might be written based on
[https://docs.djangoproject.com/en/stable/topics/db/multi-db/#cross-
database-relations this assumption] in the documentation:
However, if you’re using SQLite or MySQL with MyISAM tables, there is no
enforced referential integrity; as a result, you may be able to ‘fake’
cross database foreign keys. However, this configuration is not officially
supported by Django.
but I'm not positive about that.
--
Ticket URL: <https://code.djangoproject.com/ticket/27629#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.d2504e1ccb6fd7b1d17c5a5a874e5ba0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
