From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Chris M <chris(at)none(dot)none> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: ALTER SCHEMA problem |
Date: | 2003-08-21 02:32:21 |
Message-ID: | 20030821023221.GA24904@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 19, 2003 at 21:24:50 +0800,
Chris M <chris(at)none(dot)none> wrote:
> 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.
That depends on your point of view. As far as what gets passed to the nextval
function 's work just like they do in the where clause. However the value
gets treated like the strings used to represent identifiers in SQL where
"s are used to quote identifier names.
> And I think ORACLE's syntax is better.
At some point someone will probably implement the Oracle syntax.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-08-21 03:00:35 | FW: postgresql 7.3.2 bug on date '1901-12-13' and '190 1-1 2 (fwd) |
Previous Message | pgsql-bugs | 2003-08-21 02:29:22 | Returned due to virus; Was: Re: Re: My details |