Jody Garnett wrote:
> I am waiting on:
> - patch for events (and justin is waiting on me to make him a test
> case? showing a design problem I found - two commits are issued if you
> have two datastores on the same transaction; rather than one)
The event patch has been comitted. The double commit i
I think a lot of open jiras is a good sign... that the datastore is
actually used :). But I agree, and would be up for a ticket triage in
jdbc-ng to cut those number of issues down.
Andrea Aime wrote:
> Christian Müller ha scritto:
>> I have been waiting for this mail a long time :-)
>> I was no
I am waiting on:
- patch for events (and justin is waiting on me to make him a test
case? showing a design problem I found - two commits are issued if you
have two datastores on the same transaction; rather than one)
- aggregation support; I had something but I killed it due to the
amount of duplic
Christian Müller ha scritto:
> I have been waiting for this mail a long time :-)
> I was not sure because there are a lot of jira issues but +1 !! in
> any case.
Yeah, lots of jiras indeed, yet if you wait to release software without
any bugs or missing feature you'll release it... never.
F
I have been waiting for this mail a long time :-)
I was not sure because there are a lot of jira issues but +1 !! in any
case.
For the db2 side, the issues left are additional features (blob, aggregate
functions, partial 3d support,).
Andrea Aime writes:
> Hi,
> I was think
Hi,
I was thinking about trunk and I'm wondering if there is
anything still missing in order to graduate jdbc-ng and
push down the old jdbc datastores in unsupported land
for a release cycle?
The full list of issues against jdbc-ng is here:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset
