| From: | Justin <zzzzz(dot)graf(at)gmail(dot)com> |
|---|---|
| To: | Mike Dewhirst <miked(at)dewhirst(dot)com(dot)au> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Zahid Rahman <zahidr1000(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Renaming sequences |
| Date: | 2019-12-19 00:01:39 |
| Message-ID: | CALL-XeMhtNXRH-eLC1NEHKKYHOPmjv5_s87YzW+y8OAwWH-6wg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
as the saying goes "can not see it from house", or "when it breaks you keep
both pieces". (hope my humor comes across)
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,
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcel Ruff | 2019-12-20 18:18:45 | Disk space consumption: character varying(255) versus text used for index |
| Previous Message | Renee | 2019-12-18 15:47:05 | Re: Re[2]: Health warning: |