Re: Postgres Updating only changed columns against entire row
| От | Ron |
|---|---|
| Тема | Re: Postgres Updating only changed columns against entire row |
| Дата | |
| Msg-id | 88ffa330-e0e2-f9da-2469-97dbeca66906@gmail.com обсуждение исходный текст |
| Ответ на | Postgres Updating only changed columns against entire row (Debraj Manna <subharaj.manna@gmail.com>) |
| Список | pgsql-admin |
On 7/29/22 01:19, Debraj Manna wrote:
I'll counter with my own question: why would you go through all the extra coding effort (which leads to more places that you can make a mistake, like accidentally typing
Also, the parentheses are superfluous in this case.
Let's say I have a table like below
CREATE TABLE empl( id SERIAL PRIMARY KEY, name VARCHAR NOT NULL, address VARCHAR NOT NULL, status int NOT NULL, metadata varchar NOT NULL );and it has data like
(2, 'tuk', 'ind', 1, 'meta') ... (200, 'tuka', 'eng', 2, 'meta2')
update empl set status = 2 where (id = 2);update empl set status = 2, name='tuk', address='ind', metadata='meta' where (id = 2);Can someone let me know if there are any advantages of doing #1 over #2 assuming there are no other indices or triggers on the table? Which is generally preferred?
I'll counter with my own question: why would you go through all the extra coding effort (which leads to more places that you can make a mistake, like accidentally typing
metadata='meeta')?Also, the parentheses are superfluous in this case.
--
Angular momentum makes the world go 'round.
Angular momentum makes the world go 'round.
В списке pgsql-admin по дате отправления: