Should we fix this or document it somewhere? It is the issue of
pg_get_serial_sequence handling upper/lower case differently for its two
arguments, if I remember correctly.
---
Christopher Kings-Lynne wrote:
> > Right. Fro
Right. From a bare-functionality point of view there's nothing wrong
with it, it just seems inconsistent and therefore likely to trip someone
up in future.
But it seems no one else cares, so I'll shut up about it ...
I'm happy to have it fixed or changed :) I was just pointing out why it
was lik
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >> pg_get_serial_sequence() does dequoting/downcasing on its relation-name
> >> argument, but not on its column-name argument.
>
> > I presume the reason for that is that the first paramater can be qualified:
>
> Right. From
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> pg_get_serial_sequence() does dequoting/downcasing on its relation-name
>> argument, but not on its column-name argument.
> I presume the reason for that is that the first paramater can be qualified:
Right. From a bare-functionality point of
pg_get_serial_sequence() does dequoting/downcasing on its relation-name
argument, but not on its column-name argument.
regression=# create table "FOO" ("Ff1" serial);
NOTICE: CREATE TABLE will create implicit sequence "FOO_Ff1_seq" for serial column "FOO.Ff1"
CREATE TABLE
regression=# select pg_ge
pg_get_serial_sequence() does dequoting/downcasing on its relation-name
argument, but not on its column-name argument.
regression=# create table "FOO" ("Ff1" serial);
NOTICE: CREATE TABLE will create implicit sequence "FOO_Ff1_seq" for serial column
"FOO.Ff1"
CREATE TABLE
regression=# select pg_
