Hi Michael/Rick,
Minor clarification. OpenJPA does not include any support for MaxDB, regardless of whether you're generating tables or reading / updating data.
Args.
That doesn't mean that it won't work, but you are off the beaten path.
ok, lets see.
OpenJPA uses different DBDictionary classes for each database (these are similar to Hibernate's Dialect classes). If you do not specify one in your persistence.xml file OpenJPA will take it's best guess based on the url (among other things).
Yes did not specify it.
My guess (and I think Rick was heading in this direction too) is that in the non-working case OpenJPA chose the DB2Dictionary which is not compatible with MaxDB. Take a look at the logs in your working environment and you should see something like this : 3597 mdr-pu INFO [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc. . ."
Ah ok, couldn't find any log entry, but i tested some DBDictionary values myself. "oracle" and "hsql" seems to work for SAP MaxDB in my case, but i have to do further testing.
It probably won't be the DB2Dictionary from Rick's email. You can set this in persistence.xml by using the
yes definitly, db2 value does not work.
openjpa.jdbc.DBDictionary property name, with a value set to the class that you want to use.
thx.
As a short term workaround setting the DBDictionary to whatever you have in the working environments should work for you. For medium term, you'll probably want to write your own DBDictionary for MaxDB (start by ext
ending DBDictionary? Thx
