Re: Thoughts on how to avoid a massive integer update.
| От | Fehrle, Brian |
|---|---|
| Тема | Re: Thoughts on how to avoid a massive integer update. |
| Дата | |
| Msg-id | 8491BCF6-2163-4765-BCCF-E96B845D7427@comscore.com обсуждение исходный текст |
| Ответ на | Re: Thoughts on how to avoid a massive integer update. (Rob Sargent <robjsargent@gmail.com>) |
| Ответы |
Re: Thoughts on how to avoid a massive integer update.
|
| Список | pgsql-general |
From: Rob Sargent <robjsargent@gmail.com>
Date: Friday, May 8, 2020 at 11:05 AM
To: "Fehrle, Brian" <bfehrle@comscore.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>, "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: Thoughts on how to avoid a massive integer update.
[External Email]
Could you show an example table relationship?
It’s a simple one-to-many relationship:
*Info_table*
info_table_sid integer
*data_table*
data_table_sid integer,
info_table_id integer references info_table(info_table_sid),
Right, and now you wish to change the values in the referenced table (info_table.info_table_sid) correct?
Correct. If info_table.info_table_sid = 123 and many rows in data_table point to it, the ID needs to be changed to 456 in the info_table, as well as all the columns in the data_table.
В списке pgsql-general по дате отправления: