[Django] #31825: RenameField with db_column defined drop and recreate the same constrainsts

15 views
Skip to first unread message

Django

unread,
Jul 25, 2020, 6:05:52 AM7/25/20
to django-...@googlegroups.com
#31825: RenameField with db_column defined drop and recreate the same constrainsts
------------------------------------------------+------------------------
Reporter: iurisilvio | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | 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 |
------------------------------------------------+------------------------
RenameField with db_column should be a noop because it is only the Dajngo

--
Ticket URL: <https://code.djangoproject.com/ticket/31825>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 25, 2020, 6:19:28 AM7/25/20
to django-...@googlegroups.com
#31825: RenameField with db_column defined drop and recreate the same constrainsts
on Postgres
-------------------------------------+-------------------------------------
Reporter: iurisilvio | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 3.0
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
-------------------------------------+-------------------------------------
Description changed by iurisilvio:

Old description:

> RenameField with db_column should be a noop because it is only the Dajngo

New description:

RenameField with db_column should be a noop because it is only the Django
column that changed, the database still have the same db_column.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:1>

Django

unread,
Jul 25, 2020, 6:20:52 AM7/25/20
to django-...@googlegroups.com
#31825: RenameField with db_column defined drop and recreate the same constrainsts
on Postgres
-------------------------------------+-------------------------------------
Reporter: iurisilvio | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 3.0
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
-------------------------------------+-------------------------------------

Comment (by iurisilvio):

I did a pull request here. https://github.com/django/django/pull/13236

--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:2>

Django

unread,
Jul 25, 2020, 6:21:19 AM7/25/20
to django-...@googlegroups.com
#31825: RenameField with db_column defined drop and recreate the same constrainsts
on Postgres
-------------------------------------+-------------------------------------
Reporter: iurisilvio | Owner:
Type: | iurisilvio
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 3.0
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 iurisilvio):

* owner: nobody => iurisilvio
* status: new => assigned


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:3>

Django

unread,
Jul 25, 2020, 2:13:02 PM7/25/20
to django-...@googlegroups.com
#31825: RenameField with db_column defined drop and recreate the same constrainsts
on Postgres
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | Version: master
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 Iuri de Silvio):

* version: 3.0 => master


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:4>

Django

unread,
Jul 27, 2020, 1:53:54 AM7/27/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.

-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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 felixxm):

* cc: Simon Charette (added)
* has_patch: 0 => 1
* stage: Unreviewed => Accepted


Comment:

Thanks. See related ticket when
[https://code.djangoproject.com/ticket/29245#comment:1 Simon pointed out]
that such change (3 & 4) should be a noop.

--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:5>

Django

unread,
Jul 29, 2020, 6:33:03 AM7/29/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:6>

Django

unread,
Aug 3, 2020, 4:35:31 AM8/3/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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 Iuri de Silvio):

* needs_better_patch: 1 => 0


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:7>

Django

unread,
Aug 12, 2020, 6:31:38 AM8/12/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:8>

Django

unread,
Aug 12, 2020, 4:00:21 PM8/12/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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 Iuri de Silvio):

* needs_better_patch: 1 => 0


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:9>

Django

unread,
Aug 13, 2020, 2:40:29 AM8/13/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: assigned
Component: Migrations | 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 felixxm):

* stage: Accepted => Ready for checkin


--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:10>

Django

unread,
Aug 13, 2020, 7:43:25 AM8/13/20
to django-...@googlegroups.com
#31825: RenameField with db_column should be a noop.
-------------------------------------+-------------------------------------
Reporter: Iuri de Silvio | Owner: Iuri de
Type: | Silvio
Cleanup/optimization | Status: closed
Component: Migrations | Version: master
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 <felisiak.mariusz@…>):

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


Comment:

In [changeset:"7f4c9222dfe2f28ff8a7ffc56c28ccbadf19cf6f" 7f4c9222]:
{{{
#!CommitTicketReference repository=""
revision="7f4c9222dfe2f28ff8a7ffc56c28ccbadf19cf6f"
Fixed #31825 -- Made RenameField operation a noop for fields with
db_column.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/31825#comment:11>

Reply all
Reply to author
Forward
0 new messages