Re: [Django] #18597: `BaseInlineFormSet` should attempt to get it's queryset from it's instance related manager before falling back to it's model's default manager

[Django]

#18597: `BaseInlineFormSet` should attempt to get it's queryset from it's 
instance
related manager before falling back to it's model's default manager
-+-
 Reporter:  Simon Charette   |Owner:  Steven
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  model formset| Triage Stage:  Accepted
  inline |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Steven Johnson):

 * owner:  nobody => Steven Johnson
 * status:  new => assigned
 * version:  3.2 => dev
 * needs_tests:  1 => 0

Comment:

 Added new pull request with docs/tests:
 https://github.com/django/django/pull/17818
-- 
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/0107018d71850915-188cab5e-f25d-4086-b05f-57a66cb10df0-00%40eu-central-1.amazonses.com.

Re: [Django] #35163: sqlite3.OperationalError: no such column: django_migrations.id

[Django]

#35163: sqlite3.OperationalError: no such column: django_migrations.id
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  sqlite   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by milahu):

 > to reproduce, build ​https://github.com/milahu/archivebox/tree/django4
 with django 4.2.9 and run

 the "no such column: id" error seems to be caused by

 
https://github.com/milahu/archivebox/commit/2e9a1f473ed0abaa9618d6ed6f55aa9202d7acbb

 based on https://code.djangoproject.com/ticket/32577

 {{{
 DEFAULT_AUTO_FIELD = 'django.db.models.UUIDAutoField'
 }}}

 {{{
 class UUIDAutoField(models.fields.AutoField, models.fields.UUIDField):

 def __init__(self, *args, **kwargs):
 #kwargs['db_default'] = RandomUUID()
 #kwargs['db_default'] = uuid.uuid4()
 super().__init__(*args, **kwargs)

 def deconstruct(self):
 name, path, args, kwargs = super().deconstruct()
 #del kwargs['db_default']
 return name, path, args, kwargs

 def get_internal_type(self):
 return 'UUIDAutoField'

 def rel_db_type(self, connection):
 return models.fields.UUIDField().db_type(connection=connection)

 models.UUIDAutoField = UUIDAutoField
 }}}

 because later, i get the same "no such column: id" error, when django is
 trying to migrate this SQL table

 {{{
 class Snapshot(models.Model):

 # FIXME sqlite3.OperationalError: table new__core_snapshot has no
 column named id
 id = models.UUIDAutoField(primary_key=True, default=uuid.uuid4,
 editable=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/0107018d71227dee-93fd466c-8c15-49a0-b4b9-c9ea36ab478f-00%40eu-central-1.amazonses.com.

Re: [Django] #35163: sqlite3.OperationalError: no such column: django_migrations.id

[Django]

#35163: sqlite3.OperationalError: no such column: django_migrations.id
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  sqlite   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Tim Graham):

 I think we need a more minimal example. Perhaps if you try to put one
 together you'll find the cause of 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/0107018d711d8c26-db69c8f4-ba5d-4145-8b32-263a4b6d1328-00%40eu-central-1.amazonses.com.

Re: [Django] #35164: PermissionError: Permission denied: site-packages

[Django]

#35164: PermissionError: Permission denied: site-packages
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  database migrations  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by milahu):

 > If makemigrations is attempting to generate migrations for packages
 installed in your environment it's a symptom of a large problem

 https://github.com/django/django/pull/17816#issuecomment-1925362445

 >> It seems that one of your 3rd party packages missed including
 migrations for some model changes
 >
 >yes, i modified the app, but i did not include the new migration file
 >
 >django throwing a fatal error here is "too much"
 >
 >django should store the new migration file somewhere, where the user can
 find it
 >show an info (or warning) and continue running the app
 >
 >then, what the user does with that new migration file, is his business
-- 
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/0107018d70e1d073-1125d05d-fc0e-404b-8a78-a7de886c7950-00%40eu-central-1.amazonses.com.

Re: [Django] #35163: sqlite3.OperationalError: no such column: django_migrations.id

[Django]

#35163: sqlite3.OperationalError: no such column: django_migrations.id
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  sqlite   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by milahu):

 to reproduce, build https://github.com/milahu/archivebox/tree/django4 with
 django 4.2.9 and run

 {{{
 $ archivebox init
 $ sqlite3 index.sqlite3 .schema
 CREATE TABLE IF NOT EXISTS "django_migrations" ("app" varchar(255) NOT
 NULL, "name" varchar(255) NOT NULL, "applied" datetime NOT NULL);
 }}}

 expected: there should be an "id" column in the "django_migrations" table
-- 
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/0107018d70c17963-63c2372b-b549-4bbc-a184-21221ba0ceb2-00%40eu-central-1.amazonses.com.

Re: [Django] #29214: Invalid SQL generated when annotating a subquery with an outerref to an annotated field.

[Django]

#29214: Invalid SQL generated when annotating a subquery with an outerref to an
annotated field.
-+-
 Reporter:  Oskar Persson|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset | Triage Stage:  Accepted
  annotations|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by aysum1914):

 Well, I came here from #32839 and believe that it better explains the
 issue. I also see a 'missing FROM-clause entry for table "T5" ' error when
 using an annotated field in a subquery with OuterRef which is joined
 multiple times in the query and gets the name of T5. When I checked the
 raw query I saw that the table joined as T5 but used in the subquery as
 "T5" and then raised 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d70bf4c6e-26d283a0-0949-49ec-aa1e-716c7d149a41-00%40eu-central-1.amazonses.com.

Re: [Django] #35164: PermissionError: Permission denied: site-packages

[Django]

#35164: PermissionError: Permission denied: site-packages
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  database migrations  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Simon Charette):

 > felixxm has no interest in supporting this use case i have no time for
 pointless discussions about obvious bugs so "let someone else solve this
 problem"...

 If `makemigrations` is attempting to generate migrations for packages
 installed in your environment it's a symptom of a large problem and thus
 it doesn't justify the patch you're proposing.

 Mariusz is rightfully doing so and pointed you in the right direction.
 Please take a moment to introspect your approach in suggesting changes
 without providing details on how to reproduce your problem. These are not
 pointless discussions and you should expect to engage in such talks if you
 expect maintainers to consider your changes for inclusion and maintenance
 for the years to come.
-- 
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/0107018d70409980-ac4fa9ca-05f4-4f41-8a12-f54daa4c6d36-00%40eu-central-1.amazonses.com.

Re: [Django] #34976: startproject and startapp should provide feedback

[Django]

#34976: startproject and startapp should provide feedback
-+-
 Reporter:  Thibaud Colas|Owner:  Salvo
 Type:   |  Polizzi
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  tutorial, command,   | Triage Stage:  Accepted
  startproject, startapp |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Salvo Polizzi):

 * 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/0107018d703bf660-0fd5f4c2-cdd4-43fb-ba6b-50757857ce06-00%40eu-central-1.amazonses.com.

Re: [Django] #35164: PermissionError: Permission denied: site-packages

[Django]

#35164: PermissionError: Permission denied: site-packages
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  database migrations  | Triage Stage:
 |  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:

 Again, it is an issue in a 3rd party packages missed including migrations
 for some model changes. You should report this to their issue tracker.
-- 
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/0107018d70329d13-eb04dee0-822e-4bdd-b393-def2879f5043-00%40eu-central-1.amazonses.com.

[Django] #35164: PermissionError: Permission denied: site-packages

[Django]

#35164: PermissionError: Permission denied: site-packages
-+-
   Reporter:  milahu |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  database migrations
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 continue https://github.com/django/django/pull/17816

 currently, django is trying to write database migration files
 to the path of the app based on django

 apps based on django can be installed in read-only paths
 and then, django should not throw a fatal error

 site-packages should be treated as read-only
 runtime state belongs to $HOME/.cache/

 felixxm has no interest in supporting this use case
 i have no time for pointless discussions about obvious bugs
 so "let someone else solve this 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d702f9c73-996f0db4-ec0e-4b34-982e-f4e416000914-00%40eu-central-1.amazonses.com.

Re: [Django] #35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a db_default crashes on MySQL

[Django]

#35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a
db_default crashes on MySQL
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  mysql db_default | Triage Stage:  Ready for
  text json blob geometry|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/0107018d702b317e-63e584f1-cb43-4adc-aadd-aa195fcbe3f9-00%40eu-central-1.amazonses.com.

Re: [Django] #35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a db_default crashes on MySQL

[Django]

#35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a
db_default crashes on MySQL
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  mysql db_default | Triage Stage:  Accepted
  text json blob geometry|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d702afced-584315ed-b562-4637-a13c-a0f092ebd3c3-00%40eu-central-1.amazonses.com.

Re: [Django] #35163: sqlite3.OperationalError: no such column: django_migrations.id

[Django]

#35163: sqlite3.OperationalError: no such column: django_migrations.id
-+-
 Reporter:  milahu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  sqlite   | Triage Stage:
 |  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:   => worksforme

Comment:

 Implicit `id` is added automatically to all models. I don't think you've
 explained the issue in enough detail to confirm a bug in Django. Please
 reopen the ticket if you can debug your issue and provide details about
 why and where Django is at fault. If you're having trouble understanding
 how Django works, see TicketClosingReasons/UseSupportChannels for ways to
 get help.
-- 
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/0107018d70248b42-2bf57268-315a-4459-8262-4da670e5fcf6-00%40eu-central-1.amazonses.com.

[Django] #35163: sqlite3.OperationalError: no such column: django_migrations.id

[Django]

#35163: sqlite3.OperationalError: no such column: django_migrations.id
-+-
   Reporter:  milahu |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  sqlite
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 continue https://github.com/django/django/pull/17815

 the error is caused by a django app, trying to record an applied database
 migration
 django/db/migrations/executor.py

 workaround: add the "id" column explicitly to class Migration

 django/db/migrations/recorder.py

 {{{
 class Migration(models.Model):
 id = models.IntegerField(primary_key=True)
 app = models.CharField(max_length=255)
 name = models.CharField(max_length=255)
 applied = models.DateTimeField(default=now)
 }}}

 https://github.com/django/django/pull/17815#issuecomment-1925345512

 > Implicit id is added automatically to all models

 but that is not reflected in the sqlite schema: there is no "id" column

 so maybe this is a bug in the sqlite backend
-- 
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/0107018d701b0140-c4aa76d7-bd5a-4aa6-99be-685a7ef81a02-00%40eu-central-1.amazonses.com.

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  Moses
 |  Mugisha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dmytro Litvinov):

 * cc: Dmytro Litvinov (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/0107018d6fdc1870-eedb93ad-4d28-4ed8-8a07-57f0b7d86a16-00%40eu-central-1.amazonses.com.

Re: [Django] #29942: viewsource links to contrib.auth.forms not appearing

[Django]

#29942: viewsource links to contrib.auth.forms not appearing
---+---
 Reporter:  Yemar Nevets   |Owner:  David Smith
 Type:  Bug|   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:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by David Smith):

 * owner:  (none) => David Smith
 * needs_better_patch:  1 => 0
 * status:  new => assigned

Comment:

 [https://github.com/django/django/pull/17613 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/0107018d6fb6fd62-3278da7b-be28-4bc7-a456-fa24414b4638-00%40eu-central-1.amazonses.com.

[Django] #35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a db_default crashes on MySQL

[Django]

#35162: Adding a BinaryField, TextField, JSONField, or GeometryField with a
db_default crashes on MySQL
-+-
   Reporter:  Simon  |  Owner:  Simon Charette
  Charette   |
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Release|   Keywords:  mysql db_default
  blocker|  text json blob geometry
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 MySQL do not support literal value `DEFAULT` for these fields and requires
 them to be wrapped in parenthesis so they are considered expressions.

 This is already something we must handle when using `DEFAULT` to add
 fields with a `default` so all the backend specific logic lives in in
 `_column_default_sql` so it's only a matter of using it in
 `db_default_sql`.
-- 
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/0107018d6fad866a-bcd6b96c-1665-4760-8bbf-43cbe0477fc2-00%40eu-central-1.amazonses.com.

Re: [Django] #30686: Improve utils.text.Truncator to use a full HTML parser.

[Django]

#30686: Improve utils.text.Truncator  to use a full HTML parser.
---+---
 Reporter:  Thomas Hooper  |Owner:  David Smith
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  dev
 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 David Smith):

 * 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/0107018d6faa9f20-74a86f1f-44e5-459c-905f-c72123e81b20-00%40eu-central-1.amazonses.com.

Re: [Django] #34746: High CPU/memory consumption when a 5XX is raised with large local variables

[Django]

#34746: High CPU/memory consumption when a 5XX is raised with large local 
variables
-+-
 Reporter:  Rémi Dupré   |Owner:  Keerthi
 Type:   |  Vasan S A
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Ready for checkin => Accepted

Comment:

 You should not mark your own PRs 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/0107018d6f8ec493-9eb6312e-1504-448c-83d4-dcab0492f4f4-00%40eu-central-1.amazonses.com.

Re: [Django] #34746: High CPU/memory consumption when a 5XX is raised with large local variables

[Django]

#34746: High CPU/memory consumption when a 5XX is raised with large local 
variables
-+-
 Reporter:  Rémi Dupré   |Owner:  Keerthi
 Type:   |  Vasan S A
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Keerthi Vasan S A):

 * 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/0107018d6f4ada6b-ddbdacf2-868e-41fb-b718-16bdeab545a5-00%40eu-central-1.amazonses.com.

Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

[Django]

#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  Shafiya
 |  Adzhani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shafiya Adzhani):

 * has_patch:  0 => 1

Comment:

 Added patch here: https://github.com/django/django/pull/17814
-- 
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/0107018d6f25fc1d-dfd6078b-84ff-48e4-8f90-6b748f7b64a6-00%40eu-central-1.amazonses.com.

Re: [Django] #34038: Low text contrast and no visual cues for links within body text in admin UI

[Django]

#34038: Low text contrast and no visual cues for links within body text in 
admin UI
-+-
 Reporter:  Thibaud Colas|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast, ux |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Sarah Boyce):

 * owner:  yushan => (none)
 * status:  assigned => new
 * has_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/0107018d6e9aab2a-b1a49550-2eee-410d-99b0-ed5f7210c457-00%40eu-central-1.amazonses.com.