Chris Cleveland
Chris Cleveland
Yes, this is a better way to do it, but it introduces a backward compatibility issue. Will have to wait for a major version change.
Ok. Does it work for sqllite otherwise?
No, what I mean is, does it work ok for sqllite? Are you having any problems? On Tue, May 3, 2016 at 1:28 PM, Great Fire Wall [email protected] wrote: >...
I've done a general rewrite of generated key handling. It's in the master branch. Have a look. Bottom line: RETURN_GENERATED_KEYS is never specified unless you call the new method .generatedKeyReceiver()...
There is no built-in support for it. I've been dropping into straight JDBC to do it. ``` Connection con = database.getConnection(); PreparedStatement myInserStatement = con.prepareStatement("insert into foo (id, bar) values...
It's a mysql jdbc bug pertaining to generated keys. There is a workaround. I'm at a ballgame right now, but I'll find it when I get back. On Sat, Apr...
https://bugs.mysql.com/bug.php?id=101823 I don't recall now if there is a workaround. You could make your primary key a BigInteger. On Sat, Apr 24, 2021, 5:31 PM Chris Cleveland ***@***.***> wrote: >...
I'd rather figure out why we got the npe in the first place. Can you help me duplicate the error?
Looks like the line prop.dataType.isAssignable ... is causing the problem. Somehow the dataType isn't getting populated. Please post the code that is failing so we can see the issue.
What error message do you get when you try it?