On 09/14/2017 03:27 PM, David G. Johnston wrote:
On Thu, Sep 14, 2017 at 12:45 AM, Rafal Pietrak <rafal@xxxxxxxxx
<mailto:rafal@xxxxxxxxx>>wrote:
Hello everybody,
Can anybody help me find a way to implement an ID which:
1. guarantees being unique across multiple tables.
2. guarantees its uniqueness not only during INSERT, but also during the
lifetime of the database/application (e.i. during future UPDATES).
3. guarantees persistence of value across database
backup/restore/upgrade.
an obvious candidate - a single SERIAL() (same serial) used in every
table that needs that ID does not guarantee (2).
Isn't this what GUIDS are for?
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
