Error 1105: -128 out of range for BIGINT UNSIGNED

[niclausse]

INSERT INTO tblOmsAccountInfo (id, uid, puid, identity, org_id, org_type, name, pinyin, status, create_uid, op_uid, created_at, updated_at, deleted_at) VALUES (146, 3000028484, 3000028484, 1, 0, 0, '唐北山', 'tangbeishan', 0, 3000028484, 3000028484, '2023-02-20 15:47:01.206', '2023-02-20 15:47:01.206', NULL)";

Execute this SQL in version 0.11.0， return the 'out of range for BIGINT UNSIGNED' ERROR, but version 0.15.0 works. Can I solve it without updating version

[timsehn]

Unlikely. @fulghum ?

[fulghum]

Hey @niclausse, happy to investigate this. Can you help provide a simple repro for this? For example, can you provide the simplest create tablestatement and aninsert` statement to repro the problem? I'll take a look later today and see what I can find, but whenever we can get an exact repro commands/code to run, we can always help faster.

[niclausse]

@fulghum Thanks for your reply, the ERROR occurs when my inserting data grows. So it may be caused by memory usage? Here is my demo codes: https://github.com/niclausse/lib-examples/blob/main/testdb/mysql_test.go

[fulghum]

Hey @niclausse, sorry for the delay. I was just going through the queue and noticed you have given us a nice repro code sample. I ran that this morning and I was able to generate the same error. I only see this happen with "BIGINT UNSIGNED" and I was able to simplify the insert statements needed to generate the error to just the two inserts: IDs 127 and 128.

I tried to run that same repro with the tip of go-mysql-server, but wasn't able to repro there yet. If you get a chance to update your repro sample to use the latest version of go-mysql-server, that would be another helpful datapoint. There's a chance it might work with the latest, since I couldn't repro, but it could also be something else in the test set up of course.

I also tried to repro this with Dolt, just as another experiment. I couldn't repro with Dolt yet either.

[fulghum]

Closing this one, since we haven't heard anything back in several months. Feel free to reopen or cut us a new issue if you're still having problems and we'll be happy to help.