From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: comparing NEW and OLD (any good this way?) |
Date: | 2009-08-13 16:15:59 |
Message-ID: | 162867790908130915h32e1963dx75d73e96569a978d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> This just looks like PG missing a feature. plpgsql has much less user
> and developer time spent on it, so I'd expect to find more strangeness
> in darker corners like this.
>
this rule should be simply removed. It's not problem. The people long
time believe so row cannot be null ever. I don't know if this is from
Oracle or somewhere. SQL/PSM allows it. This semantic is little bit
difficult. There is rule so any object is NULL when all fields is NULL
too. I thing, so it's true. There is object, that has zero
information. When You thinking about it, you have to forgot any your
knowledges from languages that's knows pointers. Maybe some people has
problem, because they put in equality NULL from SQL and NULL pointer.
regards
Pavel Stehule
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Halbert | 2009-08-13 16:31:29 | Re: array syntax and geometric type syntax |
Previous Message | kbarnard | 2009-08-13 16:05:08 | Index utilization |