Postgres Pro
Downloads
Home   >   mailing lists

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

From Guyren Howe
Subject Re: Converting sql anywhere to postgres
Date
Msg-id 3fa3d5c7-67b5-444e-9bbd-4e1a8d7f549a@Spark
Whole thread Raw
In response to Re: Converting sql anywhere to postgres  (Russell Rose | Passfield Data Systems <russellrose@passfield.co.uk>)
Responses Re: Converting sql anywhere to postgres  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
Tree view
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

pgsql-general by date:

Previous
From: Amn Ojee Uw
Date:
Subject: Re: Creating a TABLESPACE
Next
From: Rob Sargent
Date:
Subject: Re: Converting sql anywhere to postgres