Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
-+-
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #21961

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5e4fa427d0045ec66a73dc824a54a355%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
-+-
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Database layer (models, ORM)


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9329005376bfd343737fadfd6c569666%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
---+
 Reporter:  gcbirzan   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anonymous):

 I think the URL should be https://groups.google.com/forum/#!topic/django-
 developers/FJMoGgtYIX4

 Anyway, it is, but this doesn't involve any default behaviour change, so
 it should be way easier.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.20119077e56c1bec91f79c60dcf075fe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
---+
 Reporter:  gcbirzan   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by mjtamlyn):

 * stage:  Unreviewed => Accepted


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.22338bbda91f6a15248b8b95b1243484%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
---+--
 Reporter:  gcbirzan   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by mjtamlyn):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is likely related to the mailing list conversation
 https://docs.djangoproject.com/en/dev/ref/django-admin/#runserver-port-or-
 address-port and the ticket #21127. Basically the consensus seems to be
 that if we do push to the database it will be a new option to `on_delete`
 in the FK declaration. This is also likely to be bundled with the removal
 of a default behaviour for `on_delete`.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.424c507da3fa19350e3f09ad6a4827bd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
---+
 Reporter:  gcbirzan   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 By default, django creates FKs without an explicit ON DELETE on the
 backend. This, if nothing else, should be configurable. If for no other
 reason that when using some transaction isolation modes, the error
 returned by the backend will be the wrong one during concurrent
 modifications:

 Table b links to table a. You insert in table b a link to ID 1 in a, at
 the same time as you delete it from a.

 With the default (at least in PostgreSQL), in REPEATABLE READ, the error
 is IntegrityError, which is wrong, since in fact you should just retry the
 transaction. In lower isolation levels, the FK is deleted (as expected),
 though, granted the on delete signals are not called.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.1937a081e50737b921f03b3b7f42d11f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.