Hi Tobias, The connectedConfiguration code is obtaining the default schema name from the connection. It looks like this is only used by the SchemaTool (and hopefully then only to be smart about the sql it generates).
If you aren't using the schema tool I think this statement can be safely skipped. There's no option to do so today, unfortunately. As a quick hack you could create your own DBDictionary extending our DB2Dictionary and override that method. I'd like to run a few tests to be sure, but this looks like something we can fix. -mike On Wed, Mar 16, 2011 at 9:09 AM, Tobias Trelle <[email protected] > wrote: > Dear Kevin, > > > Kevin Sutter wrote: > > > > database type, I'm guessing there is some other property that is > requiring > > this "ping" to the database... Thanks. > > > > I just had a look at the DB2Dictionary: > > http://svn.apache.org/viewvc/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/DB2Dictionary.java?view=markup > > Have a look at the method > > DB2Dictionary#connectedConfiguration(Connection). > > The first thing done is the mentioned database ping. It is always > performed, > even if the DB schema ist already set by the openjpa.jdbc.Schema property. > Is this really necessary? At least I'd like to be able to disable it. > > Cheers, > Tobias > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Disable-DB-ping-on-startup-tp6175609p6176662.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
