| From: | Guyren Howe <guyren(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org <pgsql-general(at)lists(dot)postgresql(dot)org>, Russell Rose | Passfield Data Systems <russellrose(at)passfield(dot)co(dot)uk> |
| Subject: | Re: Converting sql anywhere to postgres |
| Date: | 2023-08-16 18:30:19 |
| Message-ID: | 3fa3d5c7-67b5-444e-9bbd-4e1a8d7f549a@Spark |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)passfield(dot)co(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2023-08-16 19:01:04 | Re: Converting sql anywhere to postgres |
| Previous Message | Amn Ojee Uw | 2023-08-16 17:27:27 | Re: Creating a TABLESPACE |