Postgres Pro
Downloads
Home   >   mailing lists

Re: Converting sql anywhere to postgres - Mailing list pgsql-general

From Rob Sargent
Subject Re: Converting sql anywhere to postgres
Date
Msg-id 94459638-f09a-64c5-49c5-9b8462b391ab@gmail.com
Whole thread Raw
In response to Re: Converting sql anywhere to postgres  (Guyren Howe <guyren@gmail.com>)
Responses Re: Converting sql anywhere to postgres  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Tree view
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:
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

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?

pgsql-general by date:

Previous
From: Guyren Howe
Date:
Subject: Re: Converting sql anywhere to postgres
Next
From: Adrian Klaver
Date:
Subject: Re: Converting sql anywhere to postgres