> If no objection from DataNucleus, Michael will update the TCK dependencies > to version 1.1.6-SNAPSHOT for core and rdbms.
FYI 1.1.6 of core/rdbms are released. This is the final 1.1.x release. So either switch to that or switch to 2.0.0-m2, or 2.0.0-m3-SNAPSHOT > Discussion at last week's meeting suggested that all data stores > support it. Need resolution on this question to know how to proceed. You mean the datastore itself always supports a timeout ? or do you mean a JDO implementation can manage a timeout itself ? The former is clearly not the case since there are a wide variety of datastores, some file based, with APIs that don't provide such things as timeouts. RDBMS datastores do allow a timeout to be set yet JDBC is so imprecisely defined that you get an SQLException and so have no simple way of knowing that it was a timeout (without having to play around with arbitrary JDBC error numbers). PS, what is the definition of the timeout ? Is it the time taken to communicate with the datastore ? or is it the total time for the query execution (which may include compilation) ? Regards -- Andy DataNucleus (http://www.datanucleus.org)
