Re: [VOTE][PATCH] delete from the resultset using JDBC 2.0 Updatable Resultset APIs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward Rayl wrote:
>
>> I would like to submit a patch for JDBC 2.0 Updatable Resultset apis -
>> delete functionality only. Please send in your vote based on the
>> following
>> description and the attahced patch.
>>
>>
> I for one would like to see these patches applied ASAP.  I have a near
> term need for updatable resultsets in Derby for some courseware I'm
> writing.  The repository is already at head revision 106208 as of this
> writing, so I wonder if there will be any issues with these patches.  If
> these patches will not be implemented soon, I'll test using the diff's.

This is a new feature, and is in fact a "partial" feature, just delete
support for JDBC 2 updatable result sets. This then leads to the
question that is it time to branch the codeline before applying this patch?

Assuming we get a release out based around the current code (which seems
likely, Noel on the general incubator list has asked for some minor
cleanup of the release), then it seems a stable branch to support that
release and future bug fixes to it is required.

Then the main trunk would continue as the development line, with new
features being added, such as updatable result sets, XA over network
server, etc. Then at some point in the future we would need a release
that includes any newly added features.

So I would like to see this code added to Derby, but only once we have
an initial release and a branch to support it.

Dan.
PS. on the revision number of 106208, that is a global number across all
the Apache projects that are using SVN. Thus it can (and does) get
bumped a huge amount without any changes to Derby. It seems only a
couple of weeks ago it was at around 70,000, I'd love to know which
project is checking in tens of thousands of changes in a few weeks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBo5u3Iv0S4qsbfuQRAoEjAKC2D8DO4s972WfsXuH41XD0TghfqwCfYbMy
AClpCb8BCK8AE24OApZyTmE=
=O0Ai
-----END PGP SIGNATURE-----