Hello all,
I am not completely sure if this problem is to do with Vert.x and its JDBC
wrappers or Derby 10.12.1.1.
My table is defined like this:
create table pipeline_command (
id INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH
1, INCREMENT BY 1) primary key,
I am not completely sure if this problem is to do with Vert.x and its JDBC
wrappers or Derby 10.12.1.1.
Me either.
Derby throws an error while trying to interrogate the result set for updated
rows:
Caused by: ERROR 22018: Invalid character string format for type long.
at org.apache.de
Thanks Bryan,
I'll try and get a complete test case worked up.
One thing I'll note is that I *don't* get this error when I execute the
update via other means. For example, if I do it directly via SquirrelSQL,
it's fine. That's why I wonder if Vert.x is doing something wrong. However
Vert.x is usi
One thing I'll note is that I /don't/ get this error when I execute the update
via other means.
Perhaps, those other tools (Squirrel, etc.) are not using the special
form of Statement.executeUpdate() which requests that the auto-generated
keys should be made available, while the Vert.x framewor
Ok - here's my attempt at making a fairly minimal reproducible example.
https://github.com/ssadedin/DerbyDebug
Cheers,
Simon
On Tue, Mar 29, 2016 at 11:24 AM, Bryan Pendleton <
bpendleton.de...@gmail.com> wrote:
> One thing I'll note is that I /don't/ get this error when I execute the
>> updat
Hello all,
Just one more note, I made an issue for this problem:
https://issues.apache.org/jira/browse/DERBY-6880
Cheers,
Simon
On Tue, Mar 29, 2016 at 9:44 PM, Simon wrote:
> Ok - here's my attempt at making a fairly minimal reproducible example.
>
> https://github.com/ssadedin/DerbyDebug
