If the issue is support for JDBC setQueryTimeout, it appears that at
least PostgreSQL lacks support. Here are links to discussions of the
issue for a few databases.
Oracle: supported, but timing issues can affect results
http://forums.oracle.com/forums/thread.jspa?threadID=550257
PostgreSQL:
Hi,
the current spec allows specifying a query timeout on a Query, a PM or a
PMF. The PM defines the default for all Query instances of the PM and
the PMF defines the default value for all PMs of that PMF. However,
there are still three open issue in the query timeout area:
(1) query
timeouts.
The RI has distinct methods for creating Statement objects for queries
and updates already, so it shouldn't be hard to implement.
Regards,
Jörg
On 11/17/2009 09:05 AM, Michael Bouschen wrote:
> Hi,
>
> the current spec allows specifying a query timeout on a Query, a PM or
&
Hi !
Michael Bouschen wrote on 17.11.2009 09:05:24:
> query timeout in JDO
>
> Hi,
>
> the current spec allows specifying a query timeout on a Query, a PM
> or a PMF. The PM defines the default for all Query instances of the
> PM and the PMF defines the default value fo
rrent spec allows specifying a query timeout on a Query, a PM
or a PMF. The PM defines the default for all Query instances of the
PM and the PMF defines the default value for all PMs of that PMF.
However, there are still three open issue in the query timeout area:
(1) query timeout as an option
out and it either is supported or not.
Craig
On Nov 17, 2009, at 12:05 AM, Michael Bouschen wrote:
Hi,
the current spec allows specifying a query timeout on a Query, a PM
or a PMF. The PM defines the default for all Query instances of the
PM and the PMF defines the default value for all P
he optional features
> property. I don't know of a datastore that supports read and write
> timeouts separately, so the feature can simply be called
> DatastoreTimeout and it either is supported or not.
>
> Craig
>
> On Nov 17, 2009, at 12:05 AM, Michael Bouschen wrote:
>
>
