#35969: Changing output_field for GeneratedField leads to ProgrammingError with
Postgres 16.5+
-----------------------------+---------------------------------------------
Reporter: Ryan Schave | Owner: Lufafa Joshua
Type: Bug | Status: closed
Component: Migrations | Version: 5.1
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 Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"27375ad50ea3306844aab8122de13e9b3e0d1189" 27375ad5]:
{{{#!CommitTicketReference repository=""
revision="27375ad50ea3306844aab8122de13e9b3e0d1189"
Fixed #35969 -- Disallowed specifying a USING clause for altered generated
field.
PostgreSQL versions 16.5 and above no longer permit the use
of a USING clause when changing the type of a generated column.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35969#comment:10>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193d428973e-09c89db3-27a6-4b93-b600-f3b93c136b3a-000000%40eu-central-1.amazonses.com.
