#3615: Can't define forward references in fixtures using MySQL with InnoDB
-------------------------------------+-------------------------------------
               Reporter:  russellm   |          Owner:  nobody
                   Type:  Bug        |         Status:  new
              Milestone:             |      Component:  Database layer
                Version:  SVN        |  (models, ORM)
             Resolution:             |       Severity:  Normal
           Triage Stage:  Accepted   |       Keywords:  mysql innodb myisam
    Needs documentation:  0          |  reference fixture
Patch needs improvement:  1          |      Has patch:  1
                  UI/UX:  0          |    Needs tests:  0
                                     |  Easy pickings:  0
-------------------------------------+-------------------------------------

Comment (by jsdalton):

 @russellm - I don't believe so. According to the Postgres docs
 (http://www.postgresql.org/docs/current/static/sql-set-constraints.html),
 the SET CONSTRAINTS statement is *only* relevant to constraint checks
 within the current transaction, despite what the wording implies.

 > SET CONSTRAINTS sets the behavior of constraint checking within the
 current transaction. IMMEDIATE constraints are checked at the end of each
 statement. DEFERRED constraints are not checked until transaction commit.
 Each constraint has its own IMMEDIATE or DEFERRED mode.

 Furthermore:

 > This command only alters the behavior of constraints within the current
 transaction. Thus, if you execute this command outside of a transaction
 block (BEGIN/COMMIT pair), it will not appear to have any effect.

 The alterative to SET ALL is SET a list of constraints. This just effects
 constraint checking for a subset of constraints within the transaction.
 Either way, this isn't going to impact anything outside the transaction,
 let alone other tables.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/3615#comment:45>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to