[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-1000) Problem with PostgreSQL using uppercase letters in tables

[Moritz Winter (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38002#action_38002 ] 

Moritz Winter commented on HBX-1000:
------------------------------------

Is there a way to use postgresql reverse engineering with the backtick marks?

This bug is a showstopper for us and it looks really simple to solve... atm i try to figure out where to change what, maybe i can submit a patch.

> Problem with PostgreSQL using uppercase letters in tables
> ---------------------------------------------------------
>
>                 Key: HBX-1000
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000
>             Project: Hibernate Tools
>          Issue Type: Bug
>          Components: reverse-engineer
>    Affects Versions: 3.2.beta11
>         Environment: Hibernate 3.2.5.ga, Hibernate Tools 3.2.0 beta9a, PostgreSql 8.2, postgresql-8.2-506.jdbc3.jar, Eclipse 3.3.0, all running on Windows XP at the moment (including PostgreSql)
>            Reporter: Ruediger Engelberger
>
> I have problems using Hibernate tools when using upper case letters in a PostgreSQL database.
> I can configure Hibernate Tools for my local PostgreSql installation without any problems. I can access the table structure in the view Hibernate Configurations and do reverse engineering by creating XML mappings and beans. No problem.
> But when I'm using upper case characters in table names Hibernate Tools can't access the table structures any more. Hibernate Configuration shows the tables, but when I want to see the columns, it doesn't show anything. Reverse engineering also doesn't work any more.
> So, the following works:
> TABLE cms_clusterMessage
> pk_clustermessageid
> fk_clusternodeid
> messagetype
> messagedetail
> The following doesn't work:
> TABLE cms_clusterMessage
> PK_ClusterMessageId
> FK_ClusterNodeId
> MessageType
> MessageDetail
> I tried to use different JDBC drivers because I thought it could be a bug of the driver. But it wasn't. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira