Skip site navigation (1) Skip section navigation (2)

PostgreSQL No Longer Handles Mixed Case Sequences

From: Brian Harris <brian(at)harris-piper(dot)freeserve(dot)co(dot)uk>
To: pgsql-bugs(at)postgresql(dot)org
Subject: PostgreSQL No Longer Handles Mixed Case Sequences
Date: 2002-11-13 12:51:11
Message-ID: (view raw or whole thread)
Lists: pgsql-bugs
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  |         Type          |                    Modifiers
 id      | integer               | not null default nextval('T_Joint_id_seq'::text)
 epic    | character(4)          |
 code    | character(1)          | not null
 number  | integer               | not null
 price   | double precision      | not null
 costs   | double precision      | not null
 condate | date                  | not null
 effdate | date                  | not null
 comment | character varying(40) |

Unique keys: T_Joint_id_key

Triggers: RI_ConstraintTrigger_17019

sharetrack=> \ds

         List of relations

      Name       |   Type   | Owner
 T_Joint_id_seq  | sequence | brian
 T_Tester_id_seq | sequence | brian
 splits_id_seq   | sequence | brian
(3 rows)

sharetrack=> INSERT INTO "T_Tester" (epic,code,number,price,costs,condate,effdate,comment) VALUES ('37RL','B','1','36750','800','1984-12-01','1984-12-01','');

ERROR:  pg_aclcheck: class "t_tester_id_seq" not found


So although the sequence reference name is stored in mixed case in the 
table, it gets converted to lower case when processing.

Please can you advise if there is a fix available or any circumvention 
apart from redefining all affected tables.



pgsql-bugs by date

Next:From: Tom LaneDate: 2002-11-13 14:15:04
Subject: Re: Bug #816: Bad time conversion from type abstime to datetime
Previous:From: pgsql-bugsDate: 2002-11-13 12:40:48
Subject: Bug #817: Valid timezone +1300 rejected

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group