Converting sql anywhere to postgres - Mailing list pgsql-general

From Russell Rose | Passfield Data Systems
Subject Converting sql anywhere to postgres
Date
Msg-id VI1P191MB0638057C9A6AD74BD09758AAF214A@VI1P191MB0638.EURP191.PROD.OUTLOOK.COM
Whole thread Raw
Responses Re: Converting sql anywhere to postgres  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Converting sql anywhere to postgres  (Erik Wienhold <ewie@ewie.name>)
Re: Converting sql anywhere to postgres  ("Georg H." <georg-h@silentrunner.de>)
Re: Converting sql anywhere to postgres  (Guyren Howe <guyren@gmail.com>)
List pgsql-general

Hi there

 

I am trying to convert a SQL Anywhere database to postgres. Within SQL anywhere a field can have a default value of ‘last user’. This means that when you perform an update on a table, if the field is not explicitly set then the current user is used. So for instance if I have a field called mod_user in a table, but when I do an update on the table and do not set mod_user then SQL Anywhere sets the field to current_uer. I have tried to replicate this using a postgres trigger in the before update. However, if I do not set the value then it automatically picks up the value that was already in the field. Is there a way to tell the difference between me setting the value to the same as the previous value and postgres automatically picking it up.

 

If the field myfield contains the word ‘me’. Can I tell the difference between:

Update table1 set field1=’something’,myfield=’me’

And

Update table1 set field1=’something’

 

pgsql-general by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: AW: Cast INTEGER to BIT confusion
Next
From: Jason Long
Date:
Subject: PostgreSQL and GUI management