Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Rodrigo Estevao):

 Replying to [comment:8 Mariusz Felisiak ]:
 > In [changeset:"453a5bf3024ed385f95f2f9a5378d8fc03baffc2" 453a5bf3]:
 > {{{
 > #!CommitTicketReference repository=""
 revision="453a5bf3024ed385f95f2f9a5378d8fc03baffc2"
 > [3.0.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.
 >
 > The namespace of the constraint must be included when making the
 > constraint immediate.
 >
 > Regression in 22ce5d0031bd795ade081394043833e82046016c.
 >
 > Thanks Rodrigo Estevao for the report.
 >
 > Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 from master
 > }}}

 Thank you guys for your help with that!

 Cheers,
 Rodrigo

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.2086b00054e6d3d7c2eadb0b74adbb35%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"453a5bf3024ed385f95f2f9a5378d8fc03baffc2" 453a5bf3]:
 {{{
 #!CommitTicketReference repository=""
 revision="453a5bf3024ed385f95f2f9a5378d8fc03baffc2"
 [3.0.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.

 Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 from master
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.a1764b0104b3acd24c8eb696fa8664f4%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b8cb14e8a0d49a1544e3b2d6dbe40ab015bf9a8e" b8cb14e8]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8cb14e8a0d49a1544e3b2d6dbe40ab015bf9a8e"
 [3.1.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.

 Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 from master
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.f86ce265237959e9242adf79c3ef3b46%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2e8941b6f90e65ffad3f07083b8de59e8ed29767" 2e8941b6]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e8941b6f90e65ffad3f07083b8de59e8ed29767"
 Fixed #31735 -- Fixed migrations crash on namespaced inline FK addition on
 PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.c3367d0dae1cd53bb78d390cbece767b%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Simon Charette
 * status:  new => assigned
 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.66db628ffa0cbb33539de25165ea1cfb%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.6feae3300d51870e82cc6fe4075cd2a6%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 This should be solveable by making sure the schema name is included in the
 `SET CONSTRAINT` as well.

 That would result in `SET CONSTRAINTS
 "loader"."data_load_valuation_id_9af1ae91_fk_valuation_id" IMMEDIATE`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.3d20cdaedcc08f1f92e439a20e44b73c%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL.

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 Everything works properly when we remove `db_table =
 '"loader"."data_load_files"` from `DataLoadFile.Meta`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.12aff283e76dcf9c0ed7151d4f0e6138%40djangoproject.com.

Re: [Django] #31735: Migration crash when adding inline foreign key to different schema on PostgreSQL. (was: Migration problems when using intermediate (through) table on many-to-many relationship)

[Django]

#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-+-
 Reporter:  Rodrigo Estevao  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  3.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  many-to- | Triage Stage:  Accepted
  many;relationship;intermediate;table;through|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * cc: Simon Charette (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Tentatively accepted, but I'm not sure if this is a supported use case,
 see #6148.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Crashing SQL:
 {{{
 ALTER TABLE "loader"."data_load" ADD COLUMN "valuation_id" integer NOT
 NULL CONSTRAINT "data_load_valuation_id_9af1ae91_fk_valuation_id"
 REFERENCES "core"."valuation"("id") DEFERRABLE INITIALLY DEFERRED; SET
 CONSTRAINTS "data_load_valuation_id_9af1ae91_fk_valuation_id" IMMEDIATE
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.43971519b19951f1e3343aed256ddb50%40djangoproject.com.