Re: Converting sql anywhere to postgres
| От | Rob Sargent |
|---|---|
| Тема | Re: Converting sql anywhere to postgres |
| Дата | |
| Msg-id | 94459638-f09a-64c5-49c5-9b8462b391ab@gmail.com обсуждение исходный текст |
| Ответ на | Re: Converting sql anywhere to postgres (Guyren Howe <guyren@gmail.com>) |
| Ответы |
Re: Converting sql anywhere to postgres
|
| Список | pgsql-general |
On 8/16/23 12:30, Guyren Howe wrote:
For some reason, I was thinking the rule could see just the fields from the command, but you’re right; a rule won’t work. Sorry.
Guyren G Howe
On Aug 15, 2023 at 23:22 -0700, Russell Rose | Passfield Data Systems <russellrose@passfield.co.uk>, wrote:
If the original value in the user column is "me", what is the difference between "set other_column = some_value, user = 'me'" and "set other_column = some_value" at the business level?I have just had a quick look at rules and I am not sure how it can be done. Rules still use the concept of NEW and OLD. If my original row has 'myfield' set to 'me' then I don't think I can tell the difference between:
Update mytable set afield='something'
and
Update mytable set afield='something',myfield='me'
Within the rule I think NEW.myfield will be set to 'me' in both cases. Please can you explain how I can tell the difference between the two update statements
В списке pgsql-general по дате отправления: