Turning of case sensitivity for identifiers?

[Joost Kraaijeveld]

Hi all,

Is it possible to turn of the case sensitivity for tables and columns in queries (to all CAPS)? I have a (closed source) tool that I have to use (Clarion) that generates the queries and I cannot change the way the tool generates the queries.

Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: [phone]
fax: [phone]
e-mail: ***@Askesis.nl
web: www.askesis.nl

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ***@postgresql.org

[Peter Eisentraut]

Post by Joost Kraaijeveld
Is it possible to turn of the case sensitivity for tables and columns in
queries (to all CAPS)? I have a (closed source) tool that I have to use
(Clarion) that generates the queries and I cannot change the way the tool
generates the queries.

The table and column names are not actually case sensitive; they are just
folded to lower case while you apparently expect upper case. If you write
the names the same way in each command, there should not be a problem. What
problem are you actually seeing?

[Joost Kraaijeveld]

Hi Peter,

Post by Peter Eisentraut
The table and column names are not actually case sensitive;
they are just folded to lower case while you apparently expect upper case.

I am unsure of the translation of "fold". Is that the same as translate? Does that mean that if Postgresql get a query without quotes it translates the schema/column/table to lower case automatically?

Post by Peter Eisentraut
If you write the names the same way in each command, there should not be a
problem.

I cannot see how Clarion creates the queries. I have to deduct it from a log file that does not show me the query as-is but gives a "user friendly" translation of the query, without any quotes.

Post by Peter Eisentraut
What problem are you actually seeing?

Clarion checks whether the table is valid. For that, it seems to do an ODBC SQLColumns which returns the schema/table/column name in lower case while Clarino is expecting it to be uppercase. Hence it says that the table is not valid (it seems to find the table but not the columns). On a DB2 database (that has all caps names) it works.


Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: [phone]
fax: [phone]
e-mail: ***@Askesis.nl
web: www.askesis.nl

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ***@postgresql.org)

[Tom Lane]

Post by Joost Kraaijeveld
I cannot see how Clarion creates the queries.

That's easily fixed. Turn on log_statement in postgresql's
configuration file and look at the server-side log to see what Clarion
is sending.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Stephan Szabo]

Post by Joost Kraaijeveld
Is it possible to turn of the case sensitivity for tables and columns in
queries (to all CAPS)? I have a (closed source) tool that I have to use
(Clarion) that generates the queries and I cannot change the way the
tool generates the queries.

It's not currently possible to turn off case folding or to force spec
complient upper case folding. You may want to look through the archives
for the discussions if you wish to add something.


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match