From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
---|---|
To: | Сергей П (SergeiDos) <podrezov(dot)sergey(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Generated names (suffix) for constraints not described in docs |
Date: | 2024-11-15 14:13:34 |
Message-ID: | CAKAnmmJ_9OQoB03qp_FekFSDN9ntqsdnb4JzvzKmyWbZixspKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Nov 14, 2024 at 3:32 AM "Сергей П (SergeiDos)" <
podrezov(dot)sergey(at)gmail(dot)com> wrote:
> It would be logical if we formed the rules for our database developers
> identical to the internal automatic rules for forming names in the
> database, so that developers who choose the path of automatic name
> formation would receive the same result as those who set it manually in
> accordance with the described rules.
>
I think if you want a specific, known, name, you should set it yourself. As
stated earlier, the name itself is not important and the algorithm is
subject to change - the fact that the name is based off of the table is a
courtesy.
If there were no way to name your own object, I'd be more sympathetic to
this request, but automatic naming is quite avoidable.
Cheers,
Greg
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2024-11-15 15:30:59 | wal_compression = on: what is the algorithm? |
Previous Message | sheng yan | 2024-11-14 08:22:01 | Website Document Search Disadvantages for Article Titles |