I also find something magic when using sequence.
select nextval('seq_test');
and
select nextval('"seq_test"');
both refer to the same sequence: seq_test.
If I want to use a sequence with name: SEQ_TEST,
I have to write it as:
select nextval('"SEQ_TEST"');
So single quotes '...' here not like those in WHERE clause.
And I think ORACLE's syntax is better.
"Tom Lane" <tgl@sss.pgh.pa.us>
news:9363.1061099071@sss.pgh.pa.us...
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Can someone comment on this?
>
> This is unfixable as long as nextval() and friends depend on string
> parameters to represent table references. There are suggestions in
> our archives about how we might move to a more Oracle-like syntax
> (ie, table.nextval), which would expose the table reference in a way
> that could track renamings. But no one seems to have gotten really
> excited about making it happen.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
