Re: [Django] #31606: Cannot mix Exists expression with keyword arguments to When

[Django]

#31606: Cannot mix Exists expression with keyword arguments to When
-+-
 Reporter:  Ryan Heard   |Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"587b179d4115f2e4dbc425d1ae035be9eb22197b" 587b179d]:
 {{{
 #!CommitTicketReference repository=""
 revision="587b179d4115f2e4dbc425d1ae035be9eb22197b"
 Fixed #31606 -- Allowed using condition with lookups in When() expression.
 }}}

-- 
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/064.6aa430d7ea3e618e9e264d4ab1bf8e20%40djangoproject.com.

Re: [Django] #31606: Cannot mix Exists expression with keyword arguments to When

[Django]

#31606: Cannot mix Exists expression with keyword arguments to When
-+-
 Reporter:  Ryan Heard   |Owner:  Ryan
 |  Heard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Ryan Heard
 * needs_docs:  1 => 0
 * status:  new => assigned
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.8ba4c60f77623aeac5b9b21fc1748352%40djangoproject.com.

Re: [Django] #31615: Do not fail migration if postgresql extension is already installed and user is not superuser

[Django]

#31615: Do not fail migration if postgresql extension is already installed and 
user
is not superuser
-+-
 Reporter:  minusf   |Owner:  minusf
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  migration extension  | Triage Stage:  Ready for
  postgresql |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => minusf
 * needs_better_patch:  1 => 0
 * status:  new => assigned
 * needs_tests:  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/064.0f4ba4507a193054b5a6a87f0ea49326%40djangoproject.com.

[Django] #31634: Add support for With clause

[Django]

#31634: Add support for With clause
-+
   Reporter:  Ryan Heard |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Uncategorized  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Multiple database providers including [https://www.postgresql.org/docs/9.1
 /queries-with.html PostgreSQL],
 [https://dev.mysql.com/doc/refman/8.0/en/with.html MySQL] and [https
 ://oracle-base.com/articles/misc/with-clause Oracle] provide a WITH clause
 which can eliminate duplicate operations by putting results into a
 variable which can be reused.

 To add this to the Django ORM, I propose adding a {{{with_clause}}} method
 to {{{QuerySet}}}. Note that {{{with}}} is a defined keyword and cannot be
 used.

 To imagine how this might work, we can look at the example found in the
 PostgreSQL documentation and try to rebuild it using the Django ORM
 {{{
 Orders.objects.with_clause(
 
regional_sales=Orders.objects.values('region').distinct().annotate(total_sales=Sum('amount')),
 
top_regions=F('regional_sales').values('region').filter(total_sales__gt=Sum('total_sales')),
 ).filter(
 region__in=F('top_regions'),
 ).values(
 'region', 'product',
 ).distinct().annotate(
 product_units=Sum('quantity'),
 product_sales=Sum('amount'),
 )
 }}}

-- 
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/049.e7ba718e9ee7f8714419395ac1c50bad%40djangoproject.com.

Re: [Django] #31614: order_by() with expressions crashes on union() querysets.

[Django]

#31614: order_by() with expressions crashes on union() querysets.
-+-
 Reporter:  Laurent Tramoy   |Owner:  Laurent
 |  Tramoy
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"df88f24b1f5805fc388a2184e56b964746608bf4" df88f24]:
 {{{
 #!CommitTicketReference repository=""
 revision="df88f24b1f5805fc388a2184e56b964746608bf4"
 [3.1.x] Fixed #31614 -- Fixed aliases ordering by OrderBy() expressions of
 combined queryset.

 Backport of 2aac176e86204785f0f2ec4838049d8fed70870e from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.813867d32382d18058431185fbc46a08%40djangoproject.com.

Re: [Django] #31614: order_by() with expressions crashes on union() querysets.

[Django]

#31614: order_by() with expressions crashes on union() querysets.
-+-
 Reporter:  Laurent Tramoy   |Owner:  Laurent
 |  Tramoy
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"51ad767d0b31fcaa0e4ffefa2938b9184c59928a" 51ad767]:
 {{{
 #!CommitTicketReference repository=""
 revision="51ad767d0b31fcaa0e4ffefa2938b9184c59928a"
 Refs #31614 -- Added test for aliases ordering on combined querysets.
 }}}

-- 
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/064.50218cd02f0c33862110199ae45d0522%40djangoproject.com.

Re: [Django] #31614: order_by() with expressions crashes on union() querysets.

[Django]

#31614: order_by() with expressions crashes on union() querysets.
-+-
 Reporter:  Laurent Tramoy   |Owner:  Laurent
 |  Tramoy
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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:"2aac176e86204785f0f2ec4838049d8fed70870e" 2aac176e]:
 {{{
 #!CommitTicketReference repository=""
 revision="2aac176e86204785f0f2ec4838049d8fed70870e"
 Fixed #31614 -- Fixed aliases ordering by OrderBy() expressions of
 combined queryset.
 }}}

-- 
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/064.41c59bf88506757f023b7ac7fde7d2d8%40djangoproject.com.

Re: [Django] #31633: Permission objects not automatically created for ManyToMany fields without a through model

[Django]

#31633: Permission objects not automatically created for ManyToMany fields 
without
a through model
---+--
 Reporter:  Alexander Todorov  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.auth   |  Version:  3.0
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Simon Charette):

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


Comment:

 I'm not convinced we should do this, the fact many-to-many fields use
 auto-created models under the hood are an implementation details and
 Django doesn't provide other per-field permission so I don't see why we
 should do it here.

 If your app relies on such implementation detail it shouldn't be too hard
 to attach another `post_migrate` signal to create permissions for such
 auto-created models but I don't think this is something Django should
 default to.

-- 
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/066.982b2220762b8614484e53c6d5ca950a%40djangoproject.com.

Re: [Django] #31632: Single queries without transaction do not follow AUTOCOMMIT

[Django]

#31632: Single queries without transaction do not follow AUTOCOMMIT
-+-
 Reporter:  Filipe Pina  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: Florian Apolloner (added)


Comment:

 > We ended up rolling back but now, taking a better look, we pinned the
 change to this PR and the fact that our MySQL instance has the global
 autocommit set to 0.

 Just to make sure, does that mean your server was configured to disable
 autocommit but
 [https://docs.djangoproject.com/en/3.0/topics/db/transactions/#deactivate-
 transaction-management you didn't disable Django'stransaction management]?
 That could certainly lead to strange behaviour if Django thinks it's in
 autocommit mode but it actually isn't. The documentation is also pretty
 clear about why
 [https://docs.djangoproject.com/en/3.0/topics/db/transactions/#why-django-
 uses-autocommit this setup is not recommended].

-- 
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/064.61a44ca2317f3e9e6829ddd8a7766ddc%40djangoproject.com.

Re: [Django] #31621: Add "--parallel=auto" option to the "test" command.

[Django]

#31621: Add "--parallel=auto" option to the "test" command.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 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
 * stage:  Ready for checkin => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.692ee10d8d4920a91abf4835ff20449b%40djangoproject.com.

Re: [Django] #31509: Enable faulthandler automatically during tests

[Django]

#31509: Enable faulthandler automatically during tests
-+-
 Reporter:  Adam (Chainz)|Owner:  Omkar
  Johnson|  Kulkarni
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Omkar Kulkarni):

 Oh ok, sorry about that.

-- 
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/068.4d05ab4511587778487dfc8d3fce06de%40djangoproject.com.

[Django] #31633: Permission objects not automatically created for ManyToMany fields without a through model

[Django]

#31633: Permission objects not automatically created for ManyToMany fields 
without
a through model
-+
   Reporter:  Alexander Todorov  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.auth   |Version:  3.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 In `django.contrib.auth.management.create_permissions()` there's this
 snippet

 {{{
 ctypes = set()
 for klass in app_config.get_models():
 # Force looking up the content types in the current database
 # before creating foreign keys to them.
 ctype = ContentType.objects.db_manager(using).get_for_model(klass,
 for_concrete_model=False)

 ctypes.add(ctype)
 for perm in _get_all_permissions(klass._meta):
 searched_perms.append((ctype, perm))
 }}}

 This doesn't take into account automatically created models because
 `app_config.get_models()` doesn't return them.

 I think we should call `app_config.get_models(include_auto_created=True)`
 here! I can work on a PR + tests if necessary b/c I need this
 functionality.


 My use-case is that the application I am working on has been designed to
 check permission labels for the intermediate model of a m2m relationship
 b/c many of the places in the app specify a through model (that's how it
 was designed, nothing to do with the current issue).
 In the same app a newer model called Bug has a m2m relationship with Tag
 but doesn't specify a through model.

 So it is possible to design the app to use logic like "let a user only be
 able to apply tags to a TestPlan, without being able to edit the 2 related
 objects", however it is not possible to design "let a user be able to
 apply tags to a Bug without being able to edit the 2 related objects"
 because the permissions for the intermediate model are missing.

 The above use-case looks a bit odd but actually gives us very high
 granularity and allows our users to design whatever groups they want and
 partition the permission within the system at a very granular level.

 If the proposed change isn't implemented the possible workarounds for us
 are:

 1) Specify a through model - kind of ugly, we've been trying to get away
 from these and let Django do what it is supposed to do. May break existing
 installations when they decide to upgrade.

 2) Specify a custom permission for the model - will result in a new DB
 migration and the permission will be created automatically - app code will
 be different from anything else though. Kind of inconsistent with
 everything we have so far.

 3) Redesign around the logic "if you want to modify m2m then you need
 permission to modify what would be considered a main object" - would case
 a major redesign of the entire app so that everything is consistent but
 also there's no "main object" in a many to many relationship.


 Please advise!

-- 
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/051.c77ea83091e905b3262c6d822f9cc5f3%40djangoproject.com.

Re: [Django] #31631: Use Django ORM Postgresql regex when the regex is in the database and the value is a string

[Django]

#31631: Use Django ORM Postgresql regex when the regex is in the database and 
the
value is a string
-+-
 Reporter:  Simon Junod  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  QuerySet.extra   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 Duplicate of #29702.

-- 
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/065.07ab6b862bdb8a7401898c40ad46874b%40djangoproject.com.

Re: [Django] #31509: Enable faulthandler automatically during tests

[Django]

#31509: Enable faulthandler automatically during tests
-+-
 Reporter:  Adam (Chainz)|Owner:  Omkar
  Johnson|  Kulkarni
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Ready for checkin => Accepted


Comment:

 Please don't mark your own patches as 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/068.9740ae9b2708680bb161204f5eaa7d49%40djangoproject.com.

Re: [Django] #31494: Allow test Client to re-use query string for non-GET requests when following 307/308 redirects.

[Django]

#31494: Allow test Client to re-use query string for non-GET requests when
following 307/308 redirects.
-+-
 Reporter:  Max Crowe|Owner:  Ahmad
 |  Abdallah
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  test client  | Triage Stage:  Accepted
  redirect   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ahmad A. Hussein):

 * needs_better_patch:  1 => 0
 * version:  3.0 => master


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.44b93d6a5f14343c5bc92be80f6a3519%40djangoproject.com.

Re: [Django] #31509: Enable faulthandler automatically during tests

[Django]

#31509: Enable faulthandler automatically during tests
-+-
 Reporter:  Adam (Chainz)|Owner:  Omkar
  Johnson|  Kulkarni
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Omkar Kulkarni):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_tests:  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/068.989e7d8c999028a46a3b49fdf4692112%40djangoproject.com.

Re: [Django] #31620: Support "%V" format in WeekArchiveView.

[Django]

#31620: Support "%V" format in WeekArchiveView.
+--
 Reporter:  Jakub Jagielka  |Owner:  Omkar Kulkarni
 Type:  New feature |   Status:  assigned
Component:  Generic views   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Omkar Kulkarni):

 * owner:  nobody => Omkar Kulkarni
 * 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/067.c7c7f24867c60ae97650eef6071271a1%40djangoproject.com.

[Django] #31632: Single queries without transaction do not follow AUTOCOMMIT

[Django]

#31632: Single queries without transaction do not follow AUTOCOMMIT
-+-
   Reporter:  Filipe |  Owner:  nobody
  Pina   |
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The change in this PR https://github.com/django/django/pull/10448 removed
 the transaction from single queries in `Model.save_base`.

 This broke an application we tried to upgrade from Django 2.1 to 2.2 last
 year as some operations were not persisted across DB connections.
 We ended up rolling back but now, taking a better look, we pinned the
 change to this PR and the fact that our MySQL instance has the global
 `autocommit` set to 0.

 As Django <2.2 always used transactions, this was never an issue. With
 this PR introduced, I believe this raises confusion:

 * if Django AUTOCOMMIT defaults to True, we'd expect it to behave the same
 as DB autocommit global, even if it's not exactly the same.

 As we need global autocommit to 0 to avoid careless manual operations on
 the DB (that involve related queries), we'll be working around it by using
 `OPTIONS init_command` with `set autocommit=1`.

 If this is accepted as an issue, I'd like to leave some suggestions as
 well (and I won't mind doing the PR after one is chosen):

 * MySQL global autocommit setting detected as database `feature`
 * If said feature is `False` and `OPTIONS AUTOCOMMIT` is True, init
 connection with `set autocommit=1`

 Or

 * Always init connection with `set autocommit=OPTIONS[AUTOCOMMIT]`

 Or, the most agnostic one, I suppose

 * In `Model.save_base`, if AUTOCOMMIT=True, wrap single queries with
 transaction as well.

-- 
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/049.b67edc200e912e875f80c0dcf953bf53%40djangoproject.com.

Re: [Django] #6933: You cannot search with spaces if search_fields is declared with "^"

[Django]

#6933: You cannot search with spaces if search_fields is declared with "^"
-+-
 Reporter:  Martín Conte Mac |Owner:  diafour
  Donell  |
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  newforms-
 |  admin
 Severity:  Normal   |   Resolution:
 Keywords:  nfa-someday yandex-  | Triage Stage:  Accepted
  sprint ep2008  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alix Léger):

 [https://github.com/django/django/pull/ 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/100.702849d5b514479364166eb66232e768%40djangoproject.com.

[Django] #31631: Use Django ORM Postgresql regex when the regex is in the database and the value is a string

[Django]

#31631: Use Django ORM Postgresql regex when the regex is in the database and 
the
value is a string
-+-
   Reporter:  Biganon|  Owner:  nobody
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  3.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  QuerySet.extra
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I refer to [https://stackoverflow.com/questions/39797077/use-django-orm-
 postgresql-regex-when-the-regex-is-in-the-database-and-the-value this SO
 question] and in accordance with the docs, I open a ticket to request the
 inclusion of a way to search by regex (when the regex is in the database,
 not the other way around) using Django's ORM.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.d37244ff4841bffbef37ca14e518a2e3%40djangoproject.com.

Re: [Django] #31627: Could there be an "--exclude" option to "startproject/startapp"?

[Django]

#31627: Could there be an "--exclude" option to "startproject/startapp"?
-+-
 Reporter:  Jourdan Rodrigues|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jourdan Rodrigues):

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


-- 
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/074.7cc5a0f434aaa9c0b7040aa37e21e43d%40djangoproject.com.

Re: [Django] #31627: Could there be an "--exclude" option to "startproject/startapp"?

[Django]

#31627: Could there be an "--exclude" option to "startproject/startapp"?
-+-
 Reporter:  Jourdan Rodrigues|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jourdan Rodrigues):

 Replying to [comment:1 felixxm]:
 > Can you describe your use case? I'm not sure why you need to keep
 undesired files in project templates.

 I placed my use case in the description: I have a `.travis.yml` that's is
 meant to test the template, but it's not part of the template.

-- 
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/074.a389a1808fbb17e4169d2ec6fc21174c%40djangoproject.com.

Re: [Django] #31621: Add "--parallel=auto" option to the "test" command.

[Django]

#31621: Add "--parallel=auto" option to the "test" command.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 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 Ahmad A. Hussein):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch looks good

-- 
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/068.c7d5c62968ae234dff315cbaaf9551f0%40djangoproject.com.

Re: [Django] #31629: Sites framework post_migrate signal overwrites user created site.

[Django]

#31629: Sites framework post_migrate signal overwrites user created site.
---+--
 Reporter:  Tom Carrick|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.sites  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tom Carrick):

 You are right. Looking again, my data migration was wrong: it was assuming
 the site was already there.

-- 
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/065.23df177ce211e0804c056fd760c4c4ef%40djangoproject.com.

Re: [Django] #31626: Add asgi support to runserver

[Django]

#31626: Add asgi support to runserver
-+--
 Reporter:  Joshua Massover  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Uncategorized|  Version:  3.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

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


Comment:

 I'm going to momentarily close this as `needsinfo` — let's continue the
 discussion on the forum thread: we can re-open if it's agreed to bundle
 this.

-- 
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/066.965b45b60fb10386bd18ed1618d94273%40djangoproject.com.

Re: [Django] #31629: Sites framework post_migrate signal overwrites user created site.

[Django]

#31629: Sites framework post_migrate signal overwrites user created site.
---+--
 Reporter:  Tom Carrick|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.sites  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Carlton Gibson):

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


Comment:

 Hi Tom.

 Can I ask you to clarify here? AFAICS,
 
[https://github.com/django/django/blob/33c365781abbcc1b21a31b31d95d344a174df0d5/django/contrib/sites/management.py#L20-L38
 the site creation is already behind a `not exists` conditional] — so if
 you do create a data migration the `create_default_site()` is a noop.

 Maybe I've misunderstood though...
 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/065.c9f84b23c3218f52e7f01a7dc80aeb28%40djangoproject.com.

Re: [Django] #30190: json lines (jsonl) serializer

[Django]

#30190: json lines (jsonl) serializer
--+
 Reporter:  aliva |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Serialization)  |  Version:  master
 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):

 * stage:  Unreviewed => Accepted


Comment:

 OK, thanks for updating the ticket 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/063.84f64e72eed156242b687f1b4d397d4e%40djangoproject.com.

Re: [Django] #31613: GeoModelAdmin's openlayers widget stroke width too thin for some linestrings

[Django]

#31613: GeoModelAdmin's openlayers widget stroke width too thin for some
linestrings
+
 Reporter:  Vincent Ahrend  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  3.0
 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):

 * stage:  Unreviewed => Accepted


Comment:

 Hi Vincent.

 Thanks for the report. I'll accept this based on your comments, but if you
 could upload screenshots, that would help other coming to read this.

 There's a "Attachments" section just above the form to edit the issue
 description where you can attach files.
 (You can do [https://code.djangoproject.com/wiki/WikiFormatting#Images
 inline images too].)


 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/ Here's a guide to submitting patches].

-- 
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/062.30c08295077d90a1b5b5d0aef8f1a1c8%40djangoproject.com.

Re: [Django] #31614: order_by() with expressions crashes on union() querysets.

[Django]

#31614: order_by() with expressions crashes on union() querysets.
-+-
 Reporter:  Laurent Tramoy   |Owner:  Laurent
 |  Tramoy
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 felixxm):

 * 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/064.f3e446115828d1e7726f993cd8985920%40djangoproject.com.

Re: [Django] #29138: Add ModelAdmin.autocomplete_fields support for ForeignKeys that use to_field

[Django]

#29138: Add ModelAdmin.autocomplete_fields support for ForeignKeys that use
to_field
---+--
 Reporter:  Jonathan Nye   |Owner:  Tyler Schwartz
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  autocomplete   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Carsten Fuchs):

 * cc: Carsten Fuchs (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/064.c99448bc66e68737bf2c6fa3f538677c%40djangoproject.com.