| From: | Brian Harris <brian(at)harris-piper(dot)freeserve(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL No Longer Handles Mixed Case Sequences |
| Date: | 2002-11-18 12:20:58 |
| Message-ID: | 3DD8DB2A.70702@harris-piper.freeserve.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)harris-piper(dot)freeserve(dot)co(dot)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
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Mackenzie | 2002-11-18 16:28:01 | configure |
| Previous Message | Jiang Sheng | 2002-11-18 01:48:27 | Re: Different result when using '=' and 'like' in unicode mode |