date:20221006

Re: [Django] #33990: Inconsistent capitalization of Set in assertion functions

2022-10-06 Thread Django

#33990: Inconsistent capitalization of Set in assertion functions
-+-
 Reporter:  John Litborn |Owner:  Michael
 Type:   |  Howitz
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  naming,  | Triage Stage:  Accepted
  capitalization, camelcase  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Michael Howitz):

 * needs_better_patch:  1 => 0
 * needs_docs:  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/01070183b123c915-b0772e29-fc78-4698-ae3b-00ef726c7857-00%40eu-central-1.amazonses.com.

Re: [Django] #34073: Refactor session middleware to allow easier overrides

2022-10-06 Thread Django

#34073: Refactor session middleware to allow easier overrides
--+
 Reporter:  Michael Gisi  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.sessions  |  Version:  4.1
 Severity:  Normal|   Resolution:
 Keywords:  middleware| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * cc: Adam Johnson (added)
 * stage:  Unreviewed => Accepted


Comment:

 Sounds reasonable.

-- 
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/01070183b11425c0-5fdf278c-2929-4eda-b5b6-63322df4de1e-00%40eu-central-1.amazonses.com.

Re: [Django] #32603: Add transaction handling to Changelist list_editable processing.

2022-10-06 Thread Django

#32603: Add transaction handling to Changelist list_editable processing.
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Shubh
 |  Parmar
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"7a39a691e1e3fe13588c8885a222eaa6a4648d01" 7a39a691]:
 {{{
 #!CommitTicketReference repository=""
 revision="7a39a691e1e3fe13588c8885a222eaa6a4648d01"
 Fixed #32603 -- Made ModelAdmin.list_editable use transactions.
 }}}

-- 
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/01070183b10c4738-89a81670-c461-47bb-a0e6-851445eb8429-00%40eu-central-1.amazonses.com.

Re: [Django] #33586: Cannot delete object (A) referenced by another object (B) if said object (A) has a foreign key to a custom user.

2022-10-06 Thread Django

#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
---+
 Reporter:  Jeremy Poulin  |Owner:  Bhuvnesh
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  4.0
 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
---+

Comment (by Bhuvnesh):

 Most probably this error is caused due {{{mutate_state}}} .
 In the above issue for forward migration (Up) the concrete model for
 instance of model A is
 {{{
 {'__module__': '__fake__', '__doc__': 'A(id, user)', '_meta': , 'DoesNotExist': ,
 'MultipleObjectsReturned': ,
 'id': , 'user_id':
 , 'user':
 , 'objects':
 ,
 'b_set':
 }
 }}}


 For Reverse migration (down ) the concrete model for instance of model A
 is
 {{{
 {'__module__': '__fake__', '__doc__': 'A(id, user)', '_meta': , 'DoesNotExist': ,
 'MultipleObjectsReturned': ,
 'id': , 'user_id':
 , 'user':
 , 'objects':
 }
 }}}

 Due to this difference {{{check_rel_lookup_compatibility}}} is returning
 False.

-- 
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/01070183b109d9e8-de242128-33ac-4e64-8d90-e89597ba11e0-00%40eu-central-1.amazonses.com.

Re: [Django] #32263: squashmigrations produces incorrect result with a RenameModel on a ForeignKey target.

2022-10-06 Thread Django

#32263: squashmigrations produces incorrect result with a RenameModel on a
ForeignKey target.
-+-
 Reporter:  InvalidInterrupt |Owner:  Anvesh
 |  Mishra
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  3.1
 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 Anvesh Mishra):

 Tried running around the files, the first problem that was the creation of
 model with `ForeignKey` before the target of `ForeignKey` seems to be
 resolved due to some previous patches I guess. For the second problem it
 seems that the `RenameModel` misses the functionality where it needs to
 change the `to` parameter of the `ForeignKey` model. the
 `RenameModel.reduce()` doesn't seems to be getting called here.

-- 
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/01070183b0b9dd4d-e6d1079e-f5a6-4b6f-b833-5b0042f7b1e6-00%40eu-central-1.amazonses.com.

Re: [Django] #19726: Ordering on booleans works different with SQLite and Postgres

2022-10-06 Thread Django

#19726: Ordering on booleans works different with SQLite and Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Simon Charette):

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


Comment:

 You're not missing anything bcail.

 From the oldest versions of PostgreSQL (9.0.21 released in 2015), SQLite
 (3.9.0 released in 2015), and MySQL (5.6.25 released in 2015) I could get
 to run none of them exhibit the behaviour reported here.

 All of them ordered false values before true ones so I believe this issue
 might have been invalid all that time.

 Thanks for surfacing bcail.

-- 
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/01070183b0507a44-013ae839-99f6-4214-85fb-c4ed93b1c391-00%40eu-central-1.amazonses.com.

Re: [Django] #19726: Ordering on booleans works different with SQLite and Postgres

2022-10-06 Thread Django

#19726: Ordering on booleans works different with SQLite and Postgres
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (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 bcail):

 >>In Postgres, the true comes first
 I've been looking at this issue, and there's something weird. When I sort
 by a boolean field in postgres, I see false values first (postgresql 13):
 {{{
 playground=# \d stock_availability;
Table "public.stock_availability"
Column   |  Type   | Collation | Nullable | Default
 +-+---+--+-
  product_id | integer |   | not null |
  available  | boolean |   | not null |
 Indexes:
 "stock_availability_pkey" PRIMARY KEY, btree (product_id)

 playground=# select * from stock_availability;
  product_id | available
 +---
 100 | t
 200 | f
 300 | t
 400 | t
 500 | t
 600 | t
 700 | f
 800 | f

 playground=# select * from stock_availability order by available;
  product_id | available
 +---
 200 | f
 700 | f
 800 | f
 100 | t
 600 | t
 500 | t
 300 | t
 400 | t
 }}}

 What am I missing?

-- 
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/01070183aecd28a3-199a2e1c-a1b1-48ea-82c8-8f0264aa479c-00%40eu-central-1.amazonses.com.

[Django] #34073: Refactor session middleware to allow easier overrides

2022-10-06 Thread Django

#34073: Refactor session middleware to allow easier overrides
-+-
Reporter: Michael| Owner: nobody
Gisi |
Type: | Status: new
Cleanup/optimization |
Component: |Version: 4.1
contrib.sessions |
Severity: Normal | Keywords: middleware
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+-
I've recently needed to manipulate the session cookie domain per-request.
In order to do so, I needed to create a new middleware class inheriting
from `SessionMiddleware`, overriding the `process_response` method.

Because the middleware logic reads the domain directly from settings, the
result is a largely copy-pasted method just to change the domain being set
on the cookie. This override is also liable to break if the middleware or
settings change in future Django releases.

In contrast, `SecurityMiddleware` was much easier to override, since any
settings are loaded as instance attributes in `__init__`.

The proposed solution would consist of loading settings in the session
middleware `__init__` e.g. `self.cookie_domain =
settings.SESSION_COOKIE_DOMAIN`.

Happy to submit a PR if this seems reasonable.

--
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/01070183aeb1613d-56e81ba6-f720-4283-82a5-cd4beb9f32f3-00%40eu-central-1.amazonses.com.

Re: [Django] #32603: Add transaction handling to Changelist list_editable processing.

2022-10-06 Thread Django

#32603: Add transaction handling to Changelist list_editable processing.
-+-
 Reporter:  Vlastimil Zíma   |Owner:  Shubh
 |  Parmar
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183ae9dbd6b-d983c295-1d63-43b6-bbe5-576d357a1bb6-00%40eu-central-1.amazonses.com.

Re: [Django] #25996: Revise the Performance section in topics/http/urls

2022-10-06 Thread Django

#25996: Revise the Performance section in topics/http/urls
-+-
 Reporter:  Tzu-ping Chung   |Owner:  Ralph
 Type:   |  Reid
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 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 Ralph Reid):

 * owner:  (none) => Ralph Reid
 * 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/01070183ae6f4afb-01ecfca2-fbe6-4b81-942c-7b4debdf04a2-00%40eu-central-1.amazonses.com.

Re: [Django] #33871: JSONField with default is not detected as changed when invalidated in inlines.

2022-10-06 Thread Django

#33871: JSONField with default is not detected as changed when invalidated in
inlines.
-+-
 Reporter:  Raphael  |Owner:  JunKi
 |  Yoon
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  JSONField| Triage Stage:  Accepted
  TabularInline  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Current patch is mixing solution between forms and admin components.
 Slightly clearer tests showing the problem would probably clarify.

-- 
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/01070183adb4b64b-2a02e8b2-4369-404e-9f6b-2a87dc1e90d5-00%40eu-central-1.amazonses.com.

Re: [Django] #31150: Subquery annotations are omitted in group by query section if multiple annotation are declared

2022-10-06 Thread Django

#31150: Subquery annotations are omitted in group by query section if multiple
annotation are declared
-+-
 Reporter:  Johannes Maron   |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b7b28c7c189615543218e81319473888bc46d831" b7b28c7c]:
 {{{
 #!CommitTicketReference repository=""
 revision="b7b28c7c189615543218e81319473888bc46d831"
 Refs #31150 -- Enabled implicit GROUP BY aliases.

 This ensures implicit grouping from aggregate function annotations
 groups by uncollapsed selected aliases if supported.

 The feature is disabled on Oracle because it doesn't support 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183ad25-2977c034-ac26-4f22-8032-644bca84dfa9-00%40eu-central-1.amazonses.com.

Re: [Django] #33992: QuerySet.annotate() with subquery and aggregation crashes.

2022-10-06 Thread Django

#33992: QuerySet.annotate() with subquery and aggregation crashes.
-+-
 Reporter:  Fernando Flores  |Owner:  Simon
  Villaça|  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  database, orm,   | Triage Stage:  Ready for
  aggregation|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"3d734c09ff0138441dfe0a59010435871d17950f" 3d734c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="3d734c09ff0138441dfe0a59010435871d17950f"
 Refs #33992 -- Refactored subquery grouping logic.

 This required moving the combined queries slicing logic to the compiler
 in order to allow Query.exists() to be called at expression resolving
 time.

 It allowed for Query.exists() to be called at Exists() initialization
 time and thus ensured that get_group_by_cols() was operating on the
 terminal representation of the query that only has a single column
 selected.
 }}}

-- 
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/01070183ad2554fb-b6f6160f-d1b5-4ed0-8815-17af3a6e099f-00%40eu-central-1.amazonses.com.

Re: [Django] #30158: Subquery expressions unnecessarily added to group by

2022-10-06 Thread Django

#30158: Subquery expressions unnecessarily added to group by
-+-
 Reporter:  Jonny Fuller |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  subquery, group_by   | 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:"c6350d594c359151ee17b0c4f354bb44f28ff69e" c6350d5]:
 {{{
 #!CommitTicketReference repository=""
 revision="c6350d594c359151ee17b0c4f354bb44f28ff69e"
 Refs #30158 -- Removed alias argument for Expression.get_group_by_cols().

 Recent refactors allowed GROUP BY aliasing allowed for aliasing to be
 entirely handled by the sql.Query.set_group_by and compiler layers.
 }}}

-- 
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/01070183ad255586-7b906ad1-fda2-4c65-a36f-86deda35e1d2-00%40eu-central-1.amazonses.com.

Re: [Django] #34066: Accessing UserAdmin via to_field leads to link to PasswordResetForm being broken (404)

2022-10-06 Thread Django

#34066: Accessing UserAdmin via to_field leads to link to PasswordResetForm 
being
broken (404)
-+-
 Reporter:  Simon Kern   |Owner:  Simon
 |  Kern
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  auth, password,  | Triage Stage:  Ready for
  reset, passwordreset   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by David Sanders):

 * stage:  Accepted => Ready for checkin


Comment:

 @felixx Simon's made the requested updates, should be good for you to re-
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183ad0f5258-da65b6f6-c90a-4046-ade2-a7f17c929452-00%40eu-central-1.amazonses.com.

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

2022-10-06 Thread Django

#32210: Django Admin with Inlines not using UUIDField default value
--+
 Reporter:  Joseph Metzinger  |Owner:  Neeraj Kumar
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  3.1
 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 Carlton Gibson):

 * 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/01070183acd32203-3f7578c2-0a2b-430c-a339-fddf1ae1b336-00%40eu-central-1.amazonses.com.

Re: [Django] #34069: get_language_from_request should not fallback to settings.LANGUAGE_CODE

2022-10-06 Thread Django

#34069: get_language_from_request should not fallback to settings.LANGUAGE_CODE
-+-
 Reporter:  sergioisidoro|Owner:
 Type:   |  sergioisidoro
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  4.1
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  i18n | Triage Stage:  Accepted
  get_language_from_request  |
  middleware |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by David Sanders):

 * owner:  Aman Pandey => sergioisidoro


Comment:

 Hi Aman,

 Sorry the ticket is already being worked on by sergioisidoro :)

-- 
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/01070183acce4456-9c1bbae0-f7d5-43bf-827e-b4a7c56c3dd3-00%40eu-central-1.amazonses.com.

Re: [Django] #33308: Add psycopg3 backend

2022-10-06 Thread Django

#33308: Add psycopg3 backend
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database postgresql  | Triage Stage:  Accepted
  backend orm|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"04518e310d4552ff7595a34f5a7f93487d78a406" 04518e31]:
 {{{
 #!CommitTicketReference repository=""
 revision="04518e310d4552ff7595a34f5a7f93487d78a406"
 Refs #33308 -- Enabled explicit GROUP BY and ORDER BY aliases.

 This ensures explicit grouping from using values() before annotating an
 aggregate function groups by selected aliases if supported.

 The GROUP BY feature is disabled on Oracle because it doesn't support 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183ac94df3c-67af7fd7-e865-42c8-8b38-e496ccf12670-00%40eu-central-1.amazonses.com.

Re: [Django] #34072: django += 1 increments by 2 instead of 1

2022-10-06 Thread Django

#34072: django += 1 increments by 2 instead of 1
-+-
 Reporter:  kaushik kothiya  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  ASGI, Channel, ORM,  | Triage Stage:
  F Expiration, Race Condition   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Thanks for this ticket, however Trac is not a support channel and it's a
 support question. You can use `select_for_update()` to protect yourself
 against the race conditions (it's already mentioned in Stack Overflow's
 answers). Closing per TicketClosingReasons/UseSupportChannels.

-- 
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/01070183ac8746a5-5d80dca2-df2e-4982-9c1b-1e3bd0412ef3-00%40eu-central-1.amazonses.com.

Re: [Django] #34072: django += 1 increments by 2 instead of 1

2022-10-06 Thread Django

#34072: django += 1 increments by 2 instead of 1
-+-
 Reporter:  kaushik kothiya  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ASGI, Channel, ORM,  | Triage Stage:
  F Expiration, Race Condition   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kaushik kothiya):

 * Attachment "Screenshot_9.png" added.

 ASGI File

-- 
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/01070183ac6786d9-784f8e9d-9ed8-463e-9bf0-c3144b288568-00%40eu-central-1.amazonses.com.

Re: [Django] #34072: django += 1 increments by 2 instead of 1

2022-10-06 Thread Django

#34072: django += 1 increments by 2 instead of 1
-+-
 Reporter:  kaushikk25   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ASGI, Channel, ORM,  | Triage Stage:
  F Expiration, Race Condition   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kaushikk25):

 * Attachment "Screenshot_8.png" added.

 Code photo

-- 
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/01070183ac66beba-80bc1968-0f45-4343-bed7-784c44be686d-00%40eu-central-1.amazonses.com.

[Django] #34072: django += 1 increments by 2 instead of 1

2022-10-06 Thread Django

#34072: django += 1 increments by 2 instead of 1
-+-
   Reporter: |  Owner:  nobody
  kaushikk25 |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.2
  layer (models, ORM)|   Keywords:  ASGI, Channel, ORM,
   Severity:  Normal |  F Expiration, Race Condition
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 from django.db.models import F
 from hotel.models import Hotel

 Hotel.objects.filter(city='Chicago').update(total_like=F('total_like'+1))


 total_like += 1 increments by 2 instead of 1
 So here is my question: What kind of locking mechanisms are available to
 Django, to deal with situations similar to this?

 After installing the channel and HTTPS request also send wia asgi. but if
 the same code is in use WSGI request then working fine.

 https://stackoverflow.com/questions/68778007/django-1-increments-by-2
 -instead-of-1
 https://stackoverflow.com/questions/1030270/race-conditions-in-django

-- 
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/01070183ac6542aa-e48332fb-fc1e-4591-9bc1-ec1a7d466259-00%40eu-central-1.amazonses.com.

Re: [Django] #32244: ORM inefficiency: ModelFormSet executes a single-object SELECT query per formset instance when saving/validating

2022-10-06 Thread Django

Comment (by Carlton Gibson):

Hi powderflask — no problem. :)

> Here's why I think the Queryset / ModelChoiceField is redundant and
could be replaced by a simpler type of field...

I think the way forward here would be for you to provide a proof-of-
concept. Then folks could assess properly whether it were viable.

> … for reference, I have forms where >500 entries are being submitted, so
the DB lag is non-trivial

Sure. It's in this case that I provide pre-calculated `choices` to avoid
the overhead (as per above).

--
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/01070183ac3df691-95d78142-8c4a-4520-9add-c97af566ff36-00%40eu-central-1.amazonses.com.

Re: [Django] #33990: Inconsistent capitalization of Set in assertion functions

Re: [Django] #34073: Refactor session middleware to allow easier overrides

Re: [Django] #32603: Add transaction handling to Changelist list_editable processing.

Re: [Django] #33586: Cannot delete object (A) referenced by another object (B) if said object (A) has a foreign key to a custom user.

Re: [Django] #32263: squashmigrations produces incorrect result with a RenameModel on a ForeignKey target.

Re: [Django] #19726: Ordering on booleans works different with SQLite and Postgres

Re: [Django] #19726: Ordering on booleans works different with SQLite and Postgres

[Django] #34073: Refactor session middleware to allow easier overrides

Re: [Django] #32603: Add transaction handling to Changelist list_editable processing.

Re: [Django] #25996: Revise the Performance section in topics/http/urls

Re: [Django] #33871: JSONField with default is not detected as changed when invalidated in inlines.

Re: [Django] #31150: Subquery annotations are omitted in group by query section if multiple annotation are declared

Re: [Django] #33992: QuerySet.annotate() with subquery and aggregation crashes.

Re: [Django] #30158: Subquery expressions unnecessarily added to group by

Re: [Django] #34066: Accessing UserAdmin via to_field leads to link to PasswordResetForm being broken (404)

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

Re: [Django] #34069: get_language_from_request should not fallback to settings.LANGUAGE_CODE

Re: [Django] #33308: Add psycopg3 backend

Re: [Django] #34072: django += 1 increments by 2 instead of 1

Re: [Django] #34072: django += 1 increments by 2 instead of 1

Re: [Django] #34072: django += 1 increments by 2 instead of 1

[Django] #34072: django += 1 increments by 2 instead of 1

Re: [Django] #32244: ORM inefficiency: ModelFormSet executes a single-object SELECT query per formset instance when saving/validating

23 matches

Site Navigation

Mail list logo

Footer information