From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Hakan Tandogan <hakan42(at)gmx(dot)de> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Auto-lowercasing of column names? |
Date: | 2000-01-17 14:06:15 |
Message-ID: | Pine.GSO.4.02A.10001171503470.8593-100000@Puma.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
This is standard, documented behaviour. No way we can change that. Is
there a reason why your front-end tools cannot compare the names
case-insensitively?
On Mon, 17 Jan 2000, Hakan Tandogan wrote:
>
> Hi,
>
> I'm sending this to -hackers instead of -users because I think I'm
> asking for a new feature in psql.
>
> My Problem: If I run a sql file with create-table-statements through
> psql, all the column names get automagically lowercased. On the other hand, the
> Object-Relational-Mapping tool I'm using recreates all its objects from a
> ResultSet, getting the lowercase names, and compares them with uppercase ones,
> thus failing silently.
>
> I'm working around this issue by enclosing the column names in ",
> leading to slightly ugly ddl files (create table USERROLE ("ROLEID" serial
> PRIMARY KEY, "PERMISSION" varchar);) and the necessity to change the default
> data files (enclosing column names in insert statements with ").
>
> Would it be possible to add a flag to psql, telling it to accept the
> column names as they are in the ddl file?
>
>
> Regards,
> Hakan
>
>
>
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Jose Soares | 2000-01-17 14:17:56 | Re: [HACKERS] Re: Informix and OUTER join syntax |
Previous Message | Oliver Elphick | 2000-01-17 14:06:01 | Re: [HACKERS] Foreign keys: unexpected result from ALTER TABLE... ADD CONSTRAINT... |