Re: [Django] #26142: Provide a way for model formsets to disallow new object creation

[Django]

#26142: Provide a way for model formsets to disallow new object creation
-+---
 Reporter:  Tim Graham   |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 Parth Patil):

 Here is a link to the PR for this ticket,  please have a look
 https://github.com/django/django/pull/11580

-- 
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/067.850762d1be8aa07fce9c860e974f0837%40djangoproject.com.

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Sebastiaan ten Pas):

 Thanks for the PR Mariusz Felisiak and your initial PR Mariusz Felisiak. I
 would prefer to have the code change, as I still consider it a bug, but I
 can live with only the documentation change 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/065.449985bc2066ee4004666d9315c563ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27676: MariaDB 10.2 supports defaults for text columns

[Django]

#27676: MariaDB 10.2 supports defaults for text columns
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 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 felixxm):

 Django 3.0 will officially support MariaDB 10.1+. I think it's time to
 change this feature flag. Adam, can you resubmit your patch?

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

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak ):

 In [changeset:"506f800eadea2ab8c9d90f00278b4b03f3a9b771" 506f800e]:
 {{{
 #!CommitTicketReference repository=""
 revision="506f800eadea2ab8c9d90f00278b4b03f3a9b771"
 [2.2.x] Refs #30083 -- Added a warning about performing queries in
 pre/post_init receivers.

 Thanks Carlton Gibson the review.

 Backport of fc1182af01c391ce33d7fcf51c756829c6a11d5b 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 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/065.a34f35e1f5a60dac2594225df6018968%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak ):

 In [changeset:"fa3ae446d938455b47fc978cdfecb956b1238812" fa3ae44]:
 {{{
 #!CommitTicketReference repository=""
 revision="fa3ae446d938455b47fc978cdfecb956b1238812"
 [2.2.x] Refs #30083 -- Clarified database state of instances in
 signals.pre_init docs.

 Backport of a2e1c17f193f5017e1f6fac7d860f1f9e34d7892 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 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/065.8a6230b6d986fc6e87bae9055b51f14d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak ):

 In [changeset:"a2e1c17f193f5017e1f6fac7d860f1f9e34d7892" a2e1c17f]:
 {{{
 #!CommitTicketReference repository=""
 revision="a2e1c17f193f5017e1f6fac7d860f1f9e34d7892"
 Refs #30083 -- Clarified database state of instances in signals.pre_init
 docs.
 }}}

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

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak ):

 In [changeset:"fc1182af01c391ce33d7fcf51c756829c6a11d5b" fc1182af]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc1182af01c391ce33d7fcf51c756829c6a11d5b"
 Refs #30083 -- Added a warning about performing queries in pre/post_init
 receivers.

 Thanks Carlton Gibson the review.
 }}}

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

Re: [Django] #30593: Add support for check constraints on MariaDB 10.2+.

[Django]

#30593: Add support for check constraints on MariaDB 10.2+.
-+-
 Reporter:  felixxm  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  MariaDB, | Triage Stage:  Accepted
  constraint, check  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"1fc2c70f7613e014a31771afa537439b28dd35fb" 1fc2c70f]:
 {{{
 #!CommitTicketReference repository=""
 revision="1fc2c70f7613e014a31771afa537439b28dd35fb"
 Fixed #30593 -- Added support for check constraints on MariaDB 10.2+.
 }}}

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

Re: [Django] #10961: Allow users to override forward and reverse relationships on proxy models with !ForeignKey fields.

[Django]

#10961: Allow users to override forward and reverse relationships on proxy 
models
with !ForeignKey fields.
-+-
 Reporter:  Tai Lee  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy ForeignKey | Triage Stage:  Accepted
  reverse relationship manager   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Julien Enselme):

 * cc: Julien Enselme (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/067.ee09f7edfec6acb897d6710cb0cfb8c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25598: Add support for SCRIPT_NAME in STATIC_URL and MEDIA_URL

[Django]

#25598: Add support for SCRIPT_NAME in STATIC_URL and MEDIA_URL
-+-
 Reporter:  Dheerendra Rathor|Owner:  Oleg
 |  Kainov
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  script_name, | Triage Stage:  Accepted
  static_url, media_url  |
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 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/074.68479d3a974da4a14c38340581961c5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30083: Model instance state not correctly set when initializing a model with Model.from_db()

[Django]

#30083: Model instance state not correctly set when initializing a model with
Model.from_db()
-+-
 Reporter:  Sebastiaan ten Pas   |Owner:  Nasir
 |  Hussain
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 felixxm):

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


Comment:

 When we take into account performance doubts, `__new__()` tricky,
 additional complexity, and that we can encourage bad practices to perform
 queries in receivers of `pre_init` or `post_init` signals (hidden N+1
 queries on every queryset iteration), I think we shouldn't fix this (see
 also [https://code.djangoproject.com/ticket/18532#comment:5 Anssi's
 comment] and [https://code.djangoproject.com/ticket/30083#comment:4
 Simon's comment]). It's just not worth it. I'm going to add notes to the
 signal documentation.

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

Re: [Django] #30638: Allow the per-database TIME_ZONE option on databases that support timezones.

[Django]

#30638: Allow the per-database TIME_ZONE option on databases that support
timezones.
-+-
 Reporter:  Aymeric Augustin |Owner:  Aymeric
 |  Augustin
 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 felixxm):

 * stage:  Unreviewed => Accepted


Comment:

 I think it can be more tricky then it looks like to support connection
 with a native timezone support and in the same time returns datetimes in
 other timezone. We should avoid unnecessary conversions. It can also be
 confusing for users.

 Tentatively accepted, we can evaluate a patch. I understand that you're
 going to submit it.

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