subject:"Re\: \[Django\] #21961\: Add support for database\-level cascading options"

Re: [Django] #21961: Add support for database-level cascading options

2024-05-15 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ryan Hiebert):

 * cc: Ryan Hiebert (added)

-- 
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/0107018f7eaf3ab4-d7f6cf99-d7d7-4010-a5ff-7e1a300a8f44-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-04-15 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * needs_better_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/0107018ee1333999-65d38e71-c327-485d-9de5-f2eb9a9b563a-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-04-14 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * needs_better_patch:  1 => 0

-- 
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/0107018edd6e98b1-5d20e650-b88b-4787-ac27-1ee6ddc93efe-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-04-05 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * needs_better_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/0107018eaf2fe13a-b6d23577-2b9b-4501-930f-1327a0abdd13-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-02-19 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * needs_better_patch:  1 => 0

-- 
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/0107018dc0961609-4e49646f-31cf-46a8-bfa0-7cfbb03581d9-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-02-06 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Roman Donchenko):

 * cc: Roman Donchenko (added)

-- 
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/0107018d7ee52896-a6c7b03c-b342-4487-860e-eb3566895f09-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-12-27 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_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/0107018cab701096-279d3019-e415-41bb-9efe-178f2258a218-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-10-25 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Lily Foote):

 I think this is ready for review from a fellow now.

-- 
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/0107018b67bac5d0-b62a0901-9cc3-4062-b4ea-d7b2570d7181-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-08-24 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 - Added tests for migrations.

 **There are two issues I could not resolve after a lot of try : **
 - MySQL specific error in the test
 {{{delete.tests.DatabaseLevelOnDeleteTests.test_foreign_key_db_default}}}
 - I am not sure how to test the serializer.

-- 
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/0107018a2b07e97a-6fb013f8-5f83-4570-b08b-a3cf2f5076c7-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-08-06 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/01070189ce2b5815-1dce7bb2-ebe2-448c-8817-591cb5d60bac-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-08-05 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lo0):

 * cc: lo0 (added)


-- 
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/01070189c4effcd2-9797c941-42c0-4dfd-99a6-cfd28903b621-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-07-26 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 - Fixed the typos in the documentation and resolved the suggestions given
 by Mariusz
 - Will work on integrating the {{{DB_SET_DEFAULT}}} next, as suggested by
 Nick [https://github.com/django/django/pull/16851#discussion_r1251892923
 here]
 - But I am a not sure about the
 [https://github.com/django/django/pull/16851#pullrequestreview-1512214170
 serializer fix], some review will be helpful
 
[https://github.com/django/django/blob/745524a342fc39bd8e20a8cc1b8ecf4767d88a2f/django/db/migrations/serializer.py#L261
 here], or some suggestion over how to reproduce the issue.

-- 
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/0107018990ff967f-010939c6-0d38-435a-8226-964bc468cc19-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-07-04 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_docs:  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/010701891fee3337-cf54f10e-f539-4a1b-bbb1-e01cf21209c7-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-05-16 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


Comment:

 Replying to [comment:48 Akash Kumar Sen]:
 > Updated the patch https://github.com/django/django/pull/16851

 Hi Akash — I'm assuming this means that you want another review here so,
 I've unchecked the ''Needs documentation'' and ''Patch needs improvement''
 flags, so it will appear again on the list of patches needing review for
 you.

-- 
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/01070188287f21ba-6afe4125-6033-4d4b-92a5-e5a6fa4a2f2a-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-05-16 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Akash Kumar Sen):

 Updated the patch https://github.com/django/django/pull/16851

-- 
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/010701882874a215-8fd418b3-d8e5-4c18-a2a2-a260882772e0-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-05-15 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_docs:  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/010701881e405162-9c28892f-111e-4b5a-802d-82294884be94-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-05-12 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * needs_better_patch:  1 => 0


Comment:

 Created a new patch : https://github.com/django/django/pull/16851

-- 
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/0107018813563624-37f714f6-fabc-4f1e-8b5e-569437833c1a-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-05-10 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * owner:  (none) => Akash Kumar Sen
 * status:  new => assigned


-- 
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/0107018806396fdb-2db33e4e-d16d-49a9-8c38-7f4e8ca248d2-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2023-04-24 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Thibault => (none)
 * status:  assigned => new


-- 
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/01070187b246bff3-2d7e40a3-6e6d-4019-a10d-cadfe17d9f0a-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-11-28 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bcail):

 * cc: bcail (added)


-- 
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/01070184bf975891-c0f46fff-806c-41b1-be66-f6ee4155c9be-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-09-08 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Wobrock):

 * cc: David Wobrock (added)


-- 
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/010701831c9cff8a-dbb23362-79cd-4705-902a-c50029036d80-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-04-08 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by eduards-amped):

 * cc: eduards-amped (added)


-- 
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/010701800a062edd-593d07be-f0dd-4cd5-9fc6-73223716f6fb-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-03-09 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by John Speno):

 * cc: John Speno (added)


-- 
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/0107017f6e58840e-9983b432-b0ac-457d-b0a4-81f63ddd47eb-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-03-09 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by raydeal):

 * cc: raydeal (added)


-- 
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/0107017f6dfef227-5eacb681-132c-4c4e-98c0-a140c39f4d54-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-03-08 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Johnson):

 * cc: Adam Johnson (added)


-- 
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/0107017f688c6480-8a154f23-0776-4caf-b6ae-cb613e15f76e-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2022-02-02 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adrien Delessert):

 * cc: Adrien Delessert (added)


-- 
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/061.57bc435e77fd13c4176797882545a816%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-12-15 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Peter Thomassen):

 * cc: Peter Thomassen (added)


-- 
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/061.b506848cc5fef367362b2d72de8a3aa2%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-11-08 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Steven Mapes):

 I hit an issue today which lead me back to this ticket. In MySQL 5.7 and 8
 the default behaviour for FK constraints is RESTRICT which means that if
 you create your model with an on_delete=models.CASCADE, the SQL migration
 is created within the ON DELETE argument which means the table is created
 using the default constraint of RESTRICT.

 This means that the database will not act as intended if the models are
 not deleted in the right order things break, but more over DELETE
 statements directly on the database will break.

 This means Django should not really be considered compatible with MySQL
 5.7 or 8+ and probably older versions.

 Here's the MySQL docs - https://dev.mysql.com/doc/refman/8.0/en/create-
 table-foreign-keys.html#foreign-key-referential-actions
 "RESTRICT: Rejects the delete or update operation for the parent table.
 Specifying RESTRICT (or NO ACTION) is the same as omitting the ON DELETE
 or ON UPDATE clause."

 This means if you work on a project that requires actions to be taken at a
 database level you have to manually drop and recreate the foreign keys

-- 
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/061.c9de2d3c2fe676dc571a5b6f195832d9%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-08-13 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Florian Demmer):

 * cc: Florian Demmer (added)


-- 
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/061.c7927e0fad3c150a62a29ca9a46ea7c9%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-06-20 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  tvallois
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tvallois):

 * owner:  (none) => tvallois
 * status:  new => assigned


-- 
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/061.db86a6c2aaa2c13ee55504ae85893b93%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-06-13 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by tvallois):

 Hello,

 I'd like to contribute on this issue. I've read the whole ticket but i'm
 not sure to understand what's the current state of this patch. Looking at
 Nick's comment
 (https://github.com/django/django/pull/8661#issuecomment-624244307), some
 technical issues need to be answered or debated.

 Thanks for your answer.

-- 
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/061.ac170a7d98e685d5e358ee83fb59e4b5%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2021-01-22 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * cc: Carlton Gibson (added)


-- 
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/061.32ec40284c9b34c78e5eb9f57b5aae57%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-10-16 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hannes Ljungberg):

 * cc: Hannes Ljungberg (added)


-- 
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/061.33c85a8f31af8c5a41ccf0c4dcdc8eae%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-05-05 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_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/061.7f39a9d66c4efe2120275066c767f969%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-05-05 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Stefan):

 * owner:  Nick Stefan => (none)
 * status:  assigned => new


Comment:

 I unfortunately do not have bandwidth to work on this any longer.
 Hopefully someone else with more free time can take up the torch...

-- 
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/061.5b0e1651d8cc9f5b5dda4bb90deaac0b%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-04-01 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Stefan):

 * needs_tests:  1 => 0


-- 
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/061.2d304453ba147eafbaabc44efedd78cc%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-01-17 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_tests:  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/061.221d042d3b4018b57ce0723a2abe50d2%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-01-16 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Stefan):

 * needs_better_patch:  1 => 0


Comment:

 Code review seems to be complete, so unsetting "needs improvement".

-- 
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/061.48deb311492a25f7788fb18bfc9f8cd5%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2020-01-09 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Stefan):

 Replying to [comment:23 felixxm]:

 I noticed the patch is still set to "needs improvement". We've been going
 through code review process in github; do I leave that flag here as true
 after the code review follow ups? Or do I change that flag once code
 review fixes go through? Thanks!

-- 
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/061.1fbdd54b680183f1b8c70b3380c4be41%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2019-12-03 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_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/061.64c07fccbbaa2486dafe44e29ba7af3b%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2019-10-21 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Stefan):

 * cc: Nick Stefan (added)
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8661 PR]

-- 
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/061.39e6d67bb81119c68fd44284731b1d17%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

2019-05-11 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Adam Wróbel):

 * cc: Adam Wróbel (added)


-- 
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/061.5f1d201a87bd2d74ac3bd568141b3076%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2018-11-20 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 IvanAnishchuk):

 Just an idea, having two kwargs (on_delete/on_delete_db) is not entirely
 different from having one kwarg and two sets of constants
 (SET_NULL/SET_NULL_DB) -- we can always combine those constants like this:
 on_delete=SET_NULL|SET_NULL_DB and have the described behavior without
 adding a separate kwarg. Assuming it's appropriate in this case (although
 it is the way Q objects are used, for example) and that having such
 combinations is desirable at all (I could think of some cases but I'm not
 sure I can remember any such in any of my recent projects).

-- 
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/061.9bc2087f9f5b3d2816b6fb4d837e76c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2017-12-11 Thread Django

Comment (by Nick Stefan):

@Dylan
> or example, a very sensible scheme would be to have both
models.PROTECT_DB and models.CASCADE enabled

I do understand this desire. The existing foreign key constraints that get
added for models.CASCADE, only help you when you later go to edit a row
with one of those not valid foreign keys. It wont enforce / protect you
when models.CASCADE doesn't get all of the rows it should have. I hadn't
considered that there could be a desire for DB_DELETE that is completely
outside performance desires.

Is that a fair characterization?

--
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/061.9663db902935fa46de8c08591390c8be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2017-12-11 Thread Django

Comment (by Dylan Young):

I see what you're saying.

I still think there is value to the in-app deletion policy (without the
need to "roll your own") alongside a DB-enforced deletion policy. For
example, a very sensible scheme would be to have both models.PROTECT_DB
and models.CASCADE enabled, whereas (correct me if I'm mistaken) your
scheme *only* allows allow DO_NOTHING in combination with any `_DB`
setting, which has the nasty side-effect of suppressing signals.

This could still be done in your scheme of course (and can be done now),
but it involves either a custom migration... or a bit of hacking of the
migration system, and this creates a disparity between model definition
and model implementation in the DB, not to mention the extra coding
effort.

A context manager for bypassing the ORM deletion policy would also be a
nicety (this already exists I think, but I can't recall 100%).

Alternatively a syntax that allows ORing the `*_DB` flags with the
standard ORM `on_delete` flags could be used, but I think a separate kwarg
is cleaner.

I'm curious too if there's any significant performance gain to be had from
simulating the delete (without actually deleting) in the ORM in order to
correctly fire the signals, but letting the DB deal with the actual
deletion. This would probably mean that the signal ordering would be
slightly different (all pre-delete signals would fire, followed by all
post-delete signals).

In any case, this is actually a huge problem for Django where a small bulk
deletion (say 100 rows) can take hours, and I would be thankful for any
resolution to the problem.

--
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/061.8d5f9077e89bdebf2abb67749f2285ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2017-12-06 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Nick Stefan):

 Hi Dylan.

 I think your thoughts do make logical sense in response to Carl. However,
 that proposal was written a long time ago (it was circa 2014). I think
 most of that "ambiguity"  discussed then comes from 2014 DBs not
 supporting ON DELETE CASCADE. That lack of support then required the need
 to have automatic fall backs.

 In 2017, all of the supported databases should support ON DELETE CASCADE,
 so a single on_delete kwarg still makes sense to me.

 I guess there is "ambiguity" regarding signals etc, but I don't think that
 should be the case. DO_NOTHING has been a value for a long time.
 DB_CASCADE is really just DO_NOTHING plus some more SQL, so it should be
 understood that there can't be signals.

 Of course, that's just my opinion, and I admit that it might be unpopular
 based on how my PR has fared lol :).

 I opened a PR back in the summer proving the concept, and added pre check
 tests to prevent hairy situations like generic foreign keys, concrete
 model inheritance, etc: https://github.com/django/django/pull/8661 .

 --Nick

 Replying to [comment:16 Dylan Young]:
 > A separate kwarg (`on_delete_db`) is a much better proposal:
 >
 > 1) It (together with adequate documentation) eliminates *ALL* of the
 ambiguities present in the current proposal.
 > 2) When this kwarg is unspecified, it should default to the value of
 `on_delete`, ensuring as closely as possible consistency between raw
 database operations and Django operations.
 > 3) Otherwise it leaves granular control up to the user: Don't need
 delete signals (postgres should be able to support post_delete, no?)? Use
 the configuration outlined by Carl.  Need delete signals in your Django
 application, but still want sane deletion behaviour in other applications
 using your DB? Simply set `on_delete`.  Need your other applications to
 have different deletion behaviour? Just reverse the configuration outlined
 by Carl... Or any number of options?
 > 4) You could add some special flags that isolate the ORM-level deletion
 to specific DB-problematic cases (Generic Foreign Keys, Inheritance...),
 thus eliminating the overhead of python-space constraints in the majority
 of cases.
 > 5) Maybe it also makes testing Django's ORM on_delete behaviour easier?
 By adding the ability to easily cross-reference with the Database's
 internal implementation... could be wrong on that, but with `on_delete`
 set to cascade, you would expect the final deletion call of the original
 object (after all the ORM work to delete related objects) to only delete a
 single instance right? If it deletes more than expected, the error in the
 ORMs deletion emulation is exposed.
 >
 > An extra thought on Postgres:
 >
 > It seems like it should be possible to support signals with DB-level
 constraints.  Actually any DB that supports `returning` + transactions
 should be capable, no?
 >
 >
 > Replying to [comment:9 Carl Meyer]:
 > > I think we should consider introducing this feature as a totally
 separate kwarg (`on_delete_db`) rather than conflating it with the
 existing Python-level `on_delete`. The various edge cases and implicit
 fallbacks in the existing proposal worry me, and I think it would be
 better to be more explicit and clear about what is happening on the
 database level vs the Python level.
 > >
 > > Right now the contract of `on_delete` is very simple: it takes a
 Python callable which will be called when a delete cascades. There is
 nothing at all special about the built-in callables, they are just
 conveniences for common cases. The current API proposal complicates that
 contract dramatically: now you have an `on_delete` kwarg which sometimes
 accepts Python callables but can also accept magical constants which do
 something entirely different (and also have an implicit fallback
 relationship with one of the built-in callables).
 > >
 > > So under my proposal, if you want database-level cascade, you would
 specify `on_delete=models.DO_NOTHING, on_delete_db=models.DB_CASCADE` or
 similar. Sure this is a bit more verbose, but I think that's worth it for
 the gains in clarity and simpli

Re: [Django] #21961: Add support for database-level cascading options

2017-12-06 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Dylan Young):

 A separate kwarg (`on_delete_db`) is a much better proposal:

 1) It (together with adequate documentation) eliminates *ALL* of the
 ambiguities present in the current proposal.
 2) When this kwarg is unspecified, it should default to the value of
 `on_delete`, ensuring as closely as possible consistency between raw
 database operations and Django operations.
 3) Otherwise it leaves granular control up to the user: Don't need delete
 signals (postgres should be able to support post_delete, no?)? Use the
 configuration outlined by Carl.  Need delete signals in your Django
 application, but still want sane deletion behaviour in other applications
 using your DB? Simply set `on_delete`.  Need your other applications to
 have different deletion behaviour? Just reverse the configuration outlined
 by Carl... Or any number of options?
 4) You could add some special flags that isolate the ORM-level deletion to
 specific DB-problematic cases (Generic Foreign Keys, Inheritance...), thus
 eliminating the overhead of python-space constraints in the majority of
 cases.
 5) Maybe it also makes testing Django's ORM on_delete behaviour easier?
 By adding the ability to easily cross-reference with the Database's
 internal implementation... could be wrong on that, but with `on_delete`
 set to cascade, you would expect the final deletion call of the original
 object (after all the ORM work to delete related objects) to only delete a
 single instance right? If it deletes more than expected, the error in the
 ORMs deletion emulation is exposed.

 An extra thought on Postgres:

 It seems like it should be possible to support signals with DB-level
 constraints.  Actually any DB that supports `returning` + transactions
 should be capable, no?


 Replying to [comment:9 Carl Meyer]:
 > I think we should consider introducing this feature as a totally
 separate kwarg (`on_delete_db`) rather than conflating it with the
 existing Python-level `on_delete`. The various edge cases and implicit
 fallbacks in the existing proposal worry me, and I think it would be
 better to be more explicit and clear about what is happening on the
 database level vs the Python level.
 >
 > Right now the contract of `on_delete` is very simple: it takes a Python
 callable which will be called when a delete cascades. There is nothing at
 all special about the built-in callables, they are just conveniences for
 common cases. The current API proposal complicates that contract
 dramatically: now you have an `on_delete` kwarg which sometimes accepts
 Python callables but can also accept magical constants which do something
 entirely different (and also have an implicit fallback relationship with
 one of the built-in callables).
 >
 > So under my proposal, if you want database-level cascade, you would
 specify `on_delete=models.DO_NOTHING, on_delete_db=models.DB_CASCADE` or
 similar. Sure this is a bit more verbose, but I think that's worth it for
 the gains in clarity and simplicity.
 >
 > For similar reasons, I feel pretty strongly that we should NOT
 automatically fallback from db-cascade to non-db-cascade depending on the
 backend capabilities. It introduces too many differences in behavior
 depending on db backend. Trying to claim to provide cross-db portability
 when we can't really do so consistently is worse than simply not claiming
 to provide it at all. DB-level cascade (like many other "advanced" db-
 level features) is something you should only take advantage of when you
 know your code will be running on a database that supports it, full stop.
 Use of `on_delete_db` on a backend that can't support it should be an
 error.

-- 
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

Re: [Django] #21961: Add support for database-level cascading options

2017-06-22 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Nick Stefan):

 postgresql and mysql are fine. However, for SQLite to use ON DELETE, we
 would need a new OPTIONS flag. Something like:

 {{{
 settings.DATABASES.["default"]["OPTIONS"]["PRAGMA_foreign_keys"] = True
 }}}


 (which would then lead to the database wrapper running the correct SQL:
 https://sqlite.org/foreignkeys.html#fk_enable)

 If I add the pragma flag, the test suite fails quite a few tests (50+).
 Therefore, SQLite PRAGMA foreign keys, seems to be a bigger and separate
 scope. It does have its own ticket here
 https://code.djangoproject.com/ticket/14204. So postgresql and mysql are
 it, for now.

--
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/061.531685e0b89679b0e037e905cc41bc37%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2017-06-19 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Nick Stefan):

 * status:  new => assigned
 * owner:  nobody => Nick Stefan


--
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/061.52720b08345baeb2c938ca78fd2b4a4a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2017-01-19 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 André Cruz):

 * cc: andre@… (added)


--
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/061.dc994d994914ae25b126a4505c3ab344%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2016-08-02 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 edmorley):

 * cc: emorley@… (added)


--
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/061.43711b4db456239c4409873b03034731%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options

2015-10-12 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Gustavo):

 In case anyone is interested in a workaround for PostgreSQL, I created
 this simple plugin:
 https://pypi.python.org/pypi/django-postgres-delete-cascade

 That's meant as a temporary solution, until Django supports this out of
 the box.

--
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/061.c92932a1c21a931c19478d1c799909eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21961: Add support for database-level cascading options (was: ForeignKey.on_delete supports database-level cascading options)

2015-08-06 Thread Django

#21961: Add support for database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

--
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/061.75f3dd2d65c162581acfc5c78a2d9f9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

53 matches

Mail list logo