Re: Renaming sequences

Justin

I found this in my spam folder today as it came up for deletion.

On 19/12/2019 11:01 am, Justin wrote:
>
> as the saying goes "can not see it from house", or "when it breaks you
> keep both pieces".    (hope my humor comes across)

My wife also thought that was funny :)

>
> ORM  has to know the name of the sequence or it can not pre-fetch the
> sequence, or modify its values
>
> i went and looked  to double check  ORM does control the naming  see
> https://github.com/django/django/blob/master/django/db/backends/postgresql/schema.py
>
> lines 10 -13 and line 96,

Yes. In the end I made the changes with scripted psql so the sequences
match what the ORM is looking for. Postgres seems less critical because
it appears to keep track of which sequence is used by which key field
when psql does the adjustment.

>
> Postgresql auto naming  for indexes and sequences is
> tabel_column_type(idx,seq..) the ORM follows a similar logic
>
> changing names outside of the ORM will bugger the app

In this case I was trying to game the ORM because the django migration
system cannot relocate django_auth_user to myapp_common_user while
retaining existing content. This isn't an ORM problem but rather an app
design and auto-migration problem. I began the project using Django's
contributed auth app with its user model. This pre-dated Django's
current auth system with a swappable user table. New requirements forced
conversion of the user table so I can tweak a small portion of the auth
functionality.

Retro-fitting a swapped user table is v.difficult using the Django
migrations system but dead easy for a new project. Fortunately there are
plenty of giants out there to help midgets like me.

Thank you for your help

Everything is working and I'm happy

Cheers

Mike