On Sun, 8 May 2005, Tom Lane wrote:
> Why is that a good idea? In a complex application it'd be awfully easy
> to break logic that depends on such a thing.
Of course it can break. currval() can also break in a complex application
with triggers and rules that do things the developer does not expect.
There are however lots of cases where it is safe and useful. Not the least
when you want to port an application that uses similar features.
--
/Dennis Björklund
