Re: [Django] #33657: Customizable management command formatters.

[Django]

#33657: Customizable management command formatters.
-+-
 Reporter:  James Pic|Owner:  Abhinav
 |  Yadav
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  4.0
  commands)  |
 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 Mariusz Felisiak):

 * 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/010701817ff0a49f-47405704-76ea-4e40-8d49-216dc58b4f1b-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle.

[Django]

#33789: Table and colums with more then 30 chars can no longer be found on 
Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul in 't Hout):

 Here are 2 fictitious models that would have this problem.
 In our case they would have been created with a django 1.x , but for this
 bug I would think 3.2 would also reproduce.

 1. Create migration in 3.2.13
 2. Migrate
 3. Upgrade to 4.0.5
 4. Query the models

 {{{
 class LongColumnName( models.Model):
 id = models.AutoField(primary_key=True)
 name = models.CharField(max_length=100, db_index=True, unique=True)
 my_very_long_boolean_field_setting =
 models.BooleanField(default=False)

 class Meta:
 db_table = "long_column_name"
 app_label = "my_app"
 ordering = ["id", "name"]
 }}}

 And for a long table name

 {{{
 class LongTableName( models.Model):
 id = models.AutoField(primary_key=True)
 name = models.CharField(max_length=100, db_index=True, unique=True)
 short_field = models.BooleanField(default=False)

 class Meta:
 db_table = "my_very_long_table_name_for_demo"
 app_label = "my_app"
 ordering = ["id", "name"]
 }}}

 I have now gone ahead with a workaround. Which, for the above tables,
 would look like this:

 1. Get the table and column name as defined in the database for the long
 fields and table names:
 MY_VERY_LONG_BOOLEAN_FIELD76a5
 MY_VERY_LONG_TABLE_NAME_FOd906

 2.  Update the models with the table_name and db_column name attributes:

 {{{
 class LongColumnName( models.Model):
 id = models.AutoField(primary_key=True)
 name = models.CharField(max_length=100, db_index=True, unique=True)
 my_very_long_boolean_field_setting =
 models.BooleanField(default=False,
 db_column="MY_VERY_LONG_BOOLEAN_FIELD76a5"
 )

 class Meta:
 db_table = "long_column_name"
 app_label = "my_app"
 ordering = ["id", "name"]

 class LongTableName( models.Model):
 id = models.AutoField(primary_key=True)
 name = models.CharField(max_length=100, db_index=True, unique=True)
 short_field = models.BooleanField(default=False)

 class Meta:
 db_table = "MY_VERY_LONG_TABLE_NAME_FOd906"
 app_label = "my_app"
 ordering = ["id", "name"]
 }}}

 3. Create a migration
 4. Update to Django 4.0.5
 5. Fake the migration.
   I needed to auto-fake , so I added an empty apply / unapply method as
 described here (https://stackoverflow.com/questions/49150541/auto-fake-
 django-migration)

-- 
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/010701818004a62e-b4da39c1-52c0-4eaf-9c73-14dd5718b143-00%40eu-central-1.amazonses.com.

[Django] #33792: Using QuerySet.extra works while RawSQL inside annotate fails

[Django]

#33792: Using QuerySet.extra works while RawSQL inside annotate fails
-+-
   Reporter:  Shane  |  Owner:  nobody
  Ambler |
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  4.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  |
-+-
 Starting with a simplified model like this
 {{{#!python
 class Materials(models.Model):
 title = models.TextField()

 class Quotes(models.Model):
 source = models.ForeignKey('Materials', on_delete=models.CASCADE)
 quote = models.TextField()
 }}}

 I then create a form -
 {{{#!python
 class QuoteForm(forms.Form):
 source =
 forms.ModelChoiceField(queryset=Materials.objects.order_by('title').all())
 quote = forms.CharField(widget=forms.Textarea())

 def clean_source(self):
 print('Cleaning source:', self.cleaned_data)
 return self.cleaned_data['source']
 }}}

 At this point, all works well, but the `title` often starts with a numeric
 string and I want to change the sort order so that `2nd congress` sorts
 before `12th congress`.

 Using postgresql, I can change the `source` line to
 {{{#!python
 source =
 
forms.ModelChoiceField(queryset=Materials.objects.annotate(num_order=RawSQL('''cast(substring(title
 from '^([0-9]{1,10})') as integer)''',
 ('',))).order_by('num_order','title'))
 }}}

 and this provides the forms select list sorted the way I want but the form
 fails to validate with source being an invalid choice. I added the
 `clean_source()` method above to also indicate that using `RawSQL` here
 fails to call the `clean_source` method.

 If I change the source line to use `QuerySet.extra()` -
 {{{#!python
 source =
 forms.ModelChoiceField(queryset=Materials.objects.extra(select={'num_order':
 '''cast(substring(title from '^([0-9]{1,10})') as
 integer)'''}).order_by('num_order','title'))
 }}}

 I get the sort order, form validation works and `clean_source()` gets
 called.

-- 
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/01070181801008ef-64a0345c-5783-4817-9c55-08a6eabdeb54-00%40eu-central-1.amazonses.com.

Re: [Django] #33767: Ordering by F-expression resolving to a number returns wrong results

[Django]

#33767: Ordering by F-expression resolving to a number returns wrong results
-+-
 Reporter:  Florian Apolloner|Owner:  Florian
 |  Apolloner
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Florian Apolloner):

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


Comment:

 Replying to [comment:7 Simon Charette]:
 > yeah I think we should merge the two tickets together.

 Ok, I am closing this one since the other includes more context (#33768)

 > Ultimately the issue covered by
 [https://github.com/django/django/pull/15687 the submitted PR] is to make
 sure that we properly order by selected references when possible?

 Yes; while trying to fix it I looked for other problems we might have in
 that area which led to the current findings.

-- 
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/0107018180307919-b84f1ae5-4885-43ab-93f6-aaf6e55d9967-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle.

[Django]

#33789: Table and colums with more then 30 chars can no longer be found on 
Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Thanks for extra details. I'm afraid that we cannot revert Django 4.0+
 behavior because we will break all tables/columns created after this
 change 😕 What do you think about adding release notes with a link to the
 script to help identify and fix problematic identifiers? For example with
 the list of models/columns that should be updated?

-- 
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/0107018180317a4a-85cce211-0a6c-463f-99e7-2a2f3be665cd-00%40eu-central-1.amazonses.com.

Re: [Django] #33792: Using QuerySet.extra works while RawSQL inside annotate fails

[Django]

#33792: Using QuerySet.extra works while RawSQL inside annotate fails
-+-
 Reporter:  Shane Ambler |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Mariusz Felisiak):

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


Comment:

 Thanks for this report, however it's an issue in your code not in Django
 itself. It works with empty `params` (instead of a blank string):
 {{{
 num_order=RawSQL('''cast(substring(title from '^([0-9]{1,10})') as
 integer)''', params=())).order_by('num_order','title')
 }}}
 Please use one of
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels] if you have further questions.

-- 
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/01070181804006a5-5bc97f9f-4a45-4033-8cf8-7b28e81a7f15-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle.

[Django]

#33789: Table and colums with more then 30 chars can no longer be found on 
Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul in 't Hout):

 That sounds good to me. I'm sure that's going to be helpful for those
 encountering the same situation.

 I used the following sql to find out the columns and table names that are
 potential at risk for this issue.

 {{{
 select table_name,
LENGTH(table_name) as l
 from USER_TABLES
 where LENGTH(table_name) = 30
 and table_name not like 'DM$%'
 /

 select TABLE_NAME,
COLUMN_NAME,
LENGTH(COLUMN_NAME) as l
 from USER_TAB_COLUMNS
 where LENGTH(COLUMN_NAME) = 30
 and table_name not like 'DM$%'
 /
 }}}

-- 
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/010701818054b390-b03f0e99-5760-4d12-a51c-be472b9a83ea-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle.

[Django]

#33789: Table and colums with more then 30 chars can no longer be found on 
Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  oracle   | 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):

 * Attachment "fix_long_quoted_table_names.py" added.

 Script to generate RENAME TABLE for table with incorrect quoted names

-- 
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/01070181808b4395-d9e4100e-c29b-41a5-8e4f-8b794dc34967-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Table and colums with more then 30 chars can no longer be found on Oracle.

[Django]

#33789: Table and colums with more then 30 chars can no longer be found on 
Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 What do you think about
 
[https://code.djangoproject.com/attachment/ticket/33789/fix_long_quoted_table_names.py
 this script] to generate `RENAME TABLE` statements for outdated table
 names? I can create a similar one for the columns.

-- 
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/01070181808d5bd8-51bf545f-7e5c-491a-a004-edcda19f5cd6-00%40eu-central-1.amazonses.com.

Re: [Django] #32969: Improve pickling of HttpResponse instances

[Django]

#32969: Improve pickling of HttpResponse instances
-+-
 Reporter:  zatro|Owner:  Anvesh
 |  Mishra
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  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:"d7f5bfd241666c0a76e90208da1e9ef81aec44db" d7f5bfd]:
 {{{
 #!CommitTicketReference repository=""
 revision="d7f5bfd241666c0a76e90208da1e9ef81aec44db"
 Fixed #32969 -- Fixed pickling HttpResponse and subclasses.
 }}}

-- 
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/0107018180cf4166-7a6662dc-0ff6-4a6d-b29b-0065ef9db443-00%40eu-central-1.amazonses.com.

Re: [Django] #32969: Improve pickling of HttpResponse instances

[Django]

#32969: Improve pickling of HttpResponse instances
-+-
 Reporter:  zatro|Owner:  Anvesh
 Type:   |  Mishra
  Cleanup/optimization   |   Status:  closed
Component:  HTTP handling|  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):

 * type:  Bug => Cleanup/optimization


-- 
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/0107018180cf8ec6-1238308a-720a-4943-b96d-be0a2ee412e6-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle. (was: Table and colums with more then 30 chars can no longer be found on Oracle.)

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * status:  closed => new
 * resolution:  needsinfo =>
 * severity:  Normal => Release blocker
 * 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/0107018180d8232c-8cbb3b99-c5b9-4784-aaaf-784f942456df-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul in 't Hout):

 This mostly works, I had to change the following to make it work

 {{{
 rename_table_sql = "RENAME TABLE %s TO %s;"
 }}}

 to
 {{{
 rename_table_sql = "ALTER TABLE %s RENAME TO %s;"
 }}}

-- 
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/0107018180ec6a03-0982a247-dd9a-44ca-be21-fafa0ada60ce-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle. (was: Table and colums with more then 30 chars can no longer be found on Oracle.)

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * Attachment "fix_long_quoted_table_names.py" removed.

 Script to generate RENAME TABLE for table with incorrect quoted names

-- 
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/0107018180ed6705-257cf3e6-d7d3-465c-b391-ed22f95bab2f-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * Attachment "generate_rename_table_colums_new_trunc.py" 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/0107018180ed8f24-66937700-d2d8-4e7b-85b4-c4eed0f8fb72-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle. (was: Table and colums with more then 30 chars can no longer be found on Oracle.)

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * Attachment "generate_rename_table_colums_new_trunc.py" removed.


-- 
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/0107018180f14569-562a10d9-2e51-4a27-a1df-bc8a095c2316-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * Attachment "generate_rename_table_colums_new_trunc.py" 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/0107018180f16f44-bad4f240-aac1-4ca8-9a0b-e46f5f2dba86-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:11 Paul in 't Hout]:
 > This mostly works, I had to change the following to make it work
 >
 > {{{
 > rename_table_sql = "RENAME TABLE %s TO %s;"
 > }}}
 >
 > to
 > {{{
 > rename_table_sql = "ALTER TABLE %s RENAME TO %s;"
 > }}}

 Thanks for checking. I attached the new version that also should generate
 `RENAME` statements for columns. Can you take a look?

-- 
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/0107018180f27a12-8a623699-7652-4ced-bdb3-64225b5c87d9-00%40eu-central-1.amazonses.com.

[Django] #33793: Check for PASSWORD_HASHERS

[Django]

#33793: Check for PASSWORD_HASHERS
+
   Reporter:  Francisco Couzo   |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Core (System checks)  |Version:
   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 |
+
 I think it would be a good idea for the check command to check that
 `PASSWORD_HASHERS[0]` is not any of the insecure password hashers such as
 `MD5PasswordHasher` or `SHA1PasswordHasher`.

 I can take care of implementing this if there's interest on this feature.

-- 
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/0107018180f4b069-f85b6d5e-d261-4eae-82f6-21d46beecf77-00%40eu-central-1.amazonses.com.

Re: [Django] #33657: Customizable management command formatters.

[Django]

#33657: Customizable management command formatters.
-+-
 Reporter:  James Pic|Owner:  Abhinav
 |  Yadav
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  4.0
  commands)  |
 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 GitHub ):

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


Comment:

 In [changeset:"2887b9f67cadc5295ef6a0574de2c2c8fdd66905" 2887b9f]:
 {{{
 #!CommitTicketReference repository=""
 revision="2887b9f67cadc5295ef6a0574de2c2c8fdd66905"
 Fixed #33657 -- Allowed customizing formatter class of argument parsers.
 }}}

-- 
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/0107018181c15595-1075ff1f-2662-431d-a4b2-4f75b72a7e92-00%40eu-central-1.amazonses.com.

Re: [Django] #33657: Customizable management command formatters.

[Django]

#33657: Customizable management command formatters.
-+-
 Reporter:  James Pic|Owner:  Abhinav
 |  Yadav
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  4.0
  commands)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"99e5ce96c6716fe43ce1dc706a9a49b77f9e7bbc" 99e5ce96]:
 {{{
 #!CommitTicketReference repository=""
 revision="99e5ce96c6716fe43ce1dc706a9a49b77f9e7bbc"
 [4.1.x] Fixed #33657 -- Allowed customizing formatter class of argument
 parsers.

 Backport of 2887b9f67cadc5295ef6a0574de2c2c8fdd66905 from main
 }}}

-- 
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/0107018181c1e1c8-02117f84-05ac-4230-98cc-a174a4384efd-00%40eu-central-1.amazonses.com.

Re: [Django] #33028: ModelAdmin.init has self.opts, but it still nowerewhere else in django.admin.contrib.options not used

[Django]

#33028: ModelAdmin.init has self.opts, but it still nowerewhere else in
django.admin.contrib.options not used
-+-
 Reporter:  Maxim Danilov|Owner:  Marcelo
 Type:   |  Galigniana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, modeladmin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Marcelo Galigniana):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018182555b0c-dfdcf639-3b9d-4c22-a5c5-3f0519c6b53a-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paul in 't Hout):

 I've run this multiple times for our project and it turned up exactly
 those tables/columns with the problem, very nice!
 If there is a place for a caution or a note that this script should be run
 with Django 4.x in place (and not prior to upgrading) that would be great.
 That had me fooled first time around :-)

-- 
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/01070181828ac109-46c53bbb-53ae-47d5-b063-7b7dab519f4d-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned


Comment:

 Thanks for checking. I'd prepare a release note.

-- 
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/010701818290ef6f-b9db7877-ed5c-4bc5-8a7b-c4b3885e9adb-00%40eu-central-1.amazonses.com.

Re: [Django] #33028: ModelAdmin.init has self.opts, but it still nowerewhere else in django.admin.contrib.options not used

[Django]

#33028: ModelAdmin.init has self.opts, but it still nowerewhere else in
django.admin.contrib.options not used
-+-
 Reporter:  Maxim Danilov|Owner:  Marcelo
 Type:   |  Galigniana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, modeladmin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Marcelo Galigniana):

 [https://github.com/django/django/pull/15782 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/0107018182ea8aef-5ddb18e2-407d-405c-8936-d8c194749229-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 The
 
[https://code.djangoproject.com/attachment/ticket/33789/generate_rename_table_colums_new_trunc.py
 upgrade script] to generate `RENAME` DDL statements for Django 4.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/0107018184934e72-f85c67c9-2936-4dc2-a85c-bc006823a718-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
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


Comment:

 [https://github.com/django/django/pull/15784 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/0107018184a14c88-9af1382f-7a6f-4dcf-95f5-db197925ac0e-00%40eu-central-1.amazonses.com.

Re: [Django] #33028: ModelAdmin.init has self.opts, but it still nowerewhere else in django.admin.contrib.options not used

[Django]

#33028: ModelAdmin.init has self.opts, but it still nowerewhere else in
django.admin.contrib.options not used
-+-
 Reporter:  Maxim Danilov|Owner:  Marcelo
 Type:   |  Galigniana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin, modeladmin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018184daedd2-044a66e2-a5f3-424f-901f-0f12e7d52674-00%40eu-central-1.amazonses.com.

Re: [Django] #33793: Check for PASSWORD_HASHERS

[Django]

#33793: Check for PASSWORD_HASHERS
-+-
 Reporter:  Francisco Couzo  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:
  checks)|
 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 Mariusz Felisiak):

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


Comment:

 Django keeps "weak" password hashers for support with legacy systems and
 [https://docs.djangoproject.com/en/stable/topics/testing/overview
 /#password-hashing speeding up the tests]. Moreover they are not enabled
 by [https://docs.djangoproject.com/en/stable/ref/settings/#password-
 hashers default], so you must add them explicitly to the
 `PASSWORD_HASHERS`. Folks that do this should be aware of their weakness.
 IMO there is not need for a new system check.

 You can start a discussion on DevelopersMailingList if you don't agree.

-- 
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/010701818507c33c-d51bef27-672d-48d9-9f87-6d3c32f195a1-00%40eu-central-1.amazonses.com.

Re: [Django] #33789: Document changes in quoting table/colums names on Oracle.

[Django]

#33789: Document changes in quoting table/colums names on Oracle.
-+-
 Reporter:  Paul in 't Hout  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle   | 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 Carlton Gibson):

 * 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/01070181850ef8ee-a69ae72d-ed84-4ea2-a0d5-b2101068c6dd-00%40eu-central-1.amazonses.com.