db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikael Sundberg" <Mikael.Sundb...@artificial-solutions.com>
Subject RE: derby and jpa
Date Mon, 26 Jan 2009 15:01:23 GMT
Hi again, im using hibernate, and no the tables where already there
since its an existing database.



From: Lance.Andersen@Sun.COM [mailto:Lance.Andersen@Sun.COM] 
Sent: den 26 januari 2009 15:29
To: Derby Discussion
Subject: Re: derby and jpa


Hi Micke,


Which JPA implementation are you using?  Did you have the JPA
implementation create the tables for you?  JPA 2.0 will help to clarify
the case behavior semantics.  




On Jan 26, 2009, at 3:38 AM, Mikael Sundberg wrote:


I'm working on changing to JPA to talk to my database. But I seem to
have encountered some problems.

My tables named similar to: "MyTable"  so I tell my JPA class that it
belongs to "MyTable" but then it looks for MYTABLE and ofcourse it can't
find it.

When using SQL I have simply used "Select * from \"MyTable\"" to work
around that problem. But in JPA that doesn't seem to work either and it
doesn't feel like the correct way to do it either since then I bind my
JPA to only be used with derby. Other databases seem to understand that
"MyTable" is MyTable and not MYTABLE. Is there any way to work around
this problem? Except for renaming the tables since that simply isn't an



View raw message