Re: [BUGS] PostgreSQL No Longer Handles Mixed Case Sequences

2002-11-19 Thread Brian Harris
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. Reg

Re: [BUGS] PostgreSQL No Longer Handles Mixed Case Sequences

2002-11-15 Thread Tom Lane
Brian Harris <[EMAIL PROTECTED]> 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 ---(

Re: [BUGS] PostgreSQL No Longer Handles Mixed Case Sequences

2002-11-15 Thread Rod Taylor
On Wed, 2002-11-13 at 07:51, Brian Harris wrote: > Hello, > I have just updated to PostgreSQL 7.2.2. I am utilising tables with > mixed case table and field names. I can now no longer insert data into > these tables as shown by the following psql interchange: > > sharetrack=> \d "T_Joint" >

[BUGS] PostgreSQL No Longer Handles Mixed Case Sequences

2002-11-15 Thread Brian Harris
Hello, I have just updated to PostgreSQL 7.2.2. I am utilising tables with mixed case table and field names. I can now no longer insert data into these tables as shown by the following psql interchange: sharetrack=> \d "T_Joint" Table "T_Joint" Column |