From: | Adam Hardy <adam(dot)hardy(at)cyberspaceroad(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name |
Date: | 2008-02-12 15:10:19 |
Message-ID: | 47B1B6DB.8070509@cyberspaceroad.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Kris,
thanks for the advice.
Because this rules out certain important features of the JPA framework
such as native SQL queries, you may want to prioritize this issue. I
will have to use Oracle or mySQL until PostgreSQL can rectify things.
Thanks and regards
Adam
Kris Jurka on 01/02/08 20:45, wrote:
>
>
> On Fri, 1 Feb 2008, Adam Hardy wrote:
>
>> it seems to me from what you just said that PostgreSQL server and
>> JDBC driver require the schema name to be lower case deliberately,
>> and that any given name that is not all lower case is converted to
>> lower case by the server or the driver. Am I correct?
>>
>
> Anything that is not quoted is converted to lowercase. This is
> contrary to the SQL spec (it says to convert it to uppercase), but
> that's unlikely to change anytime soon. A JDBC app can portably
> detect this case by checking
> DatabaseMetaData.storesLowerCaseIdentifiers() and adjusting the other
> metadata calls appropriately.
>
> Kris Jurka
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2008-02-12 16:40:21 | Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name |
Previous Message | Gregory Stark | 2008-02-12 11:49:19 | Re: BUG #3954: Duplicate Primary Keys |