On Mon, 6 Aug 2001, Tom Lane wrote:
> * How should one invoke nextval() and friends on such a sequence?
> Perhaps we could allow people to write nextval(sequencename) and/or
> sequencename.nextval, which would expose the sequence object to the
> parser so that datatype overloading could occur.
I'm not worried about the size of the return type of
a sequence, but I like the idea of Oracle-compatible
"seq.nextval" syntax.
Matthew.