Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
От | Albe Laurenz |
---|---|
Тема | Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type? |
Дата | |
Msg-id | A737B7A37273E048B164557ADEF4A58B50FA8609@ntex2010i.host.magwien.gv.at обсуждение исходный текст |
Ответ на | Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type? (pinker <pinker@onet.eu>) |
Ответы |
Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause
be independent from data type?
Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type? |
Список | pgsql-general |
pinker wrote: > I've tried to write audit trigger which fires only when data changed, so I used "WHEN (OLD.* IS > DISTINCT FROM NEW.*)" clause as described in documentation > <http://www.postgresql.org/docs/9.4/static/sql-createtrigger.html> . Should this clause be independent > from data type? because an error occurs when I'm trying to modify row with point data type: ERROR: > could not identify an equality operator for type point I guess it is dependent on data type as it requires an equality operator, and type "point" doesn't have one. You'd have to hand-roll a comparison in this case, probably using the "same as" operator "~=". Yours, Laurenz Albe
В списке pgsql-general по дате отправления: