Within a function (and therefore within a transaction), if I UPDATE the
primary key of a table, the old value remains visible in the child table
through the end of the function. Is this
a) by design, and a good thing for some reason I don't understand
b) by design, but should be change
On Fri, 12 Nov 2004, Thomas Berg wrote:
> Within a function (and therefore within a transaction), if I UPDATE the
> primary key of a table, the old value remains visible in the child table
> through the end of the function. Is this
8.0 runs immediate triggers after each statement of a function a
