I've committed the code changes and a section to the user manual. Could use the class name for the JDBC driver, and some version information for the manual, but function wise you should be good to go once we publish a new SNAPSHOT build.
Hudson is sick for us right now, so that might take a day. If you can pick up a 2.1.0 snapshot next week and verify that I got it right that would be appreciated. -mike On Wed, Nov 3, 2010 at 9:00 AM, Michael Dick <michael.d.d...@gmail.com>wrote: > On Mon, Nov 1, 2010 at 3:58 AM, joe <fischauto...@yahoo.de> wrote: > >> Hi, >> >> >> I think (haven't verified it) that you can use the base DBDictionary >>> class - >>> this might be closer to MaxDB than Oracle or HSQL. >>> >> >> Which value i have to set for using the base DBDictionary class? >> <property name="openjpa.jdbc.DBDictionary" value="?"/> >> > > > Sorry, missed this reply and I'll confess I haven't tried it, but this > _should_ work: > <property name="openjpa.jdbc.DBDictionary" > value="org.apache.openjpa.jdbc.sql.DBDictionary"/> > > >> >> One other thing you / we can do is open a JIRA for supporting MaxDB, and >>> we >>> can add a MaxDB dictionary for you. >>> >> >> created this one: >> https://issues.apache.org/jira/browse/OPENJPA-1864 >> > > I'll take a look later this morning, should be pretty quick to add a class > for MaxDB. > > > >> >> We wouldn't be able to do much (any) >>> testing - unless MaxDB happens to be free, but we certainly could add a >>> MaxDBDictionary for you. >>> >> >> Sounds great, I would gladly test it. >> >> >> We'd want to know the format of the connection url, and a few other >>> things >>> but this should be fairly quick to include >>> >> >> jdbc:sapdb://<server>:<port7210>/<database> >> > > -mike >
