Re: PostgreSQL No Longer Handles Mixed Case Sequences - Mailing list pgsql-bugs

From Brian Harris
Subject Re: PostgreSQL No Longer Handles Mixed Case Sequences
Date
Msg-id 3DD8DB2A.70702@harris-piper.freeserve.co.uk
Whole thread Raw
In response to PostgreSQL No Longer Handles Mixed Case Sequences  (Brian Harris <brian@harris-piper.freeserve.co.uk>)
List pgsql-bugs
Tom,
Thanks for the response.
The tables were created from the output from the previous release
pg_dump program, which omitted the double quotes in the DEFAULT
nextval() clause.  I have tested the new version of pg_dump which
includes them if the sequence name contain mixed case characters.
Regards,
Brian

Tom Lane wrote:

>Brian Harris <brian@harris-piper.freeserve.co.uk> writes:
>
>
>> id      | integer               | not null default nextval('T_Joint_id_seq'::text)
>>
>>
>
>This default is wrong --- it should be
>    nextval('"T_Joint_id_seq"'::text)
>Note the quotes.
>
>            regards, tom lane
>
>
>

pgsql-bugs by date:

Previous
From: Matt Mackenzie
Date:
Subject: configure
Next
From: Kristofer Munn
Date:
Subject: Re: Bug #820: RULE on INSERT unable to access NEW