Re: Turning of case sensitivity for identifiers?

Поиск
Список
Период
Сортировка
От Joost Kraaijeveld
Тема Re: Turning of case sensitivity for identifiers?
Дата
Msg-id A3D1526C98B7C1409A687E0943EAC41001EA40@obelix.askesis.nl
обсуждение исходный текст
Ответ на Turning of case sensitivity for identifiers?  ("Joost Kraaijeveld" <J.Kraaijeveld@Askesis.nl>)
Ответы Re: Turning of case sensitivity for identifiers?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
Hi Peter,

Peter Eisentraut schreef:
> 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
withoutquotes it translates the schema/column/table to lower case automatically? 


> 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
butgives a "user friendly" translation of the query, without any quotes. 

> 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/columnname in lower case while Clarino is expecting it to be uppercase. Hence it says that the table is
notvalid (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: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl

В списке pgsql-admin по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Turning of case sensitivity for identifiers?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Point in Time Recovery