From: | Justin <zzzzz(dot)graf(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Mike Dewhirst <miked(at)dewhirst(dot)com(dot)au>, Zahid Rahman <zahidr1000(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
Subject: | Re: Renaming sequences |
Date: | 2019-12-18 14:04:08 |
Message-ID: | CALL-XeM7QFn3NBJz7VfpnAphwCU7pubwyymaQN4cd_tt+OWaPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
If using Django with its ORM it cares what the name of the sequences are
along with anything it creates.
https://docs.djangoproject.com/en/3.0/topics/db/models/
The ORM has pretty much recreated the entire Relation Database Model, DDL,
DML and abstracted it in a Object Model.
The naming schema is tablename+column+UUID . Changing the names will
bugger up the Django Migrations
to give an idea how horrible ORM can get with foreign keys and constraints
take a look at this one table created with Django ORM.
[image: image.png]
On Wed, Dec 18, 2019 at 8:53 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> On 2019-Dec-18, Mike Dewhirst wrote:
>
> > That sounds promising. I would really like the sequence name aligned
> > with the table name. I was thinking of simply editing a dump file and
> > reloading to achieve it.Is that a rational approach?
>
> I don't find it so, but it seems subjective ... YMMV.
>
> I would just copy the database (CREATE DATABASE WITH TEMPLATE) to a test
> throwaway one, do the ALTER SEQUENCE there, point the application to it,
> and see if it works. If it does, drop that database and repeat the
> ALTER SEQUENCE in your original database.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Gaston | 2019-12-18 14:23:34 | REMOVE |
Previous Message | Alvaro Herrera | 2019-12-18 13:53:08 | Re: Renaming sequences |