Hi Andrus,
Yes, LinkMove problems related to batch generated keys. The problem is
with AutoAdapter, it simply doesn't define
supportsGeneratedKeysForBatchInserts() method.
DerbyAdapter itself works fine.
On Sun, Apr 12, 2020 at 11:47 AM Andrus Adamchik wrote:
>
> Still testing the release... As
So looks like this will affect users of Derby and SQLServer who are also using
the AutoAdapter (don't know if anyone still NOT using the AutoAdapter?). I
suppose we can still release the M1, though it will not be usable for me
unfortunately until this is fixed.
Thoughts?
Andrus
> On Apr 13,
Hi Andrus,
Given this is a milestone release, I think it is fine to release with the
AutoAdapter issue. These releases aren't required or expected to be
production-ready, although that would certainly be nice. They are for
finding issues needing to be addressed, and you have. :-)
mrg
On Mon,
Been thinking more about this... This breaks basic commit operations for both
Derby and SQLServer, making it a major issue. We've never shipped releases with
known bugs like this, even milestones. On the other hand there is a workaround
- use an explicit adapter.
I am voting -0, which means tha
I would be fine with fixing it up and remaking the release, but I don’t
know how much of a hassle that is. I can find time to fix AutoAdapter in
the next two days I think.
On Mon, Apr 13, 2020 at 1:34 PM Andrus Adamchik
wrote:
> Been thinking more about this... This breaks basic commit operation
