-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SELECT LAST_INSERT_ID() appears to be limited to 32 bits... #1090
Milestone
Comments
John, Issue confirmed. |
Working on it:
|
Thanks
…On Thu, Jul 13, 2017 at 6:06 PM, René Cannaò ***@***.***> wrote:
Working on it:
mysql> insert into test values (256*256*256*256*256+101);
Query OK, 1 row affected (0.14 sec)
mysql> select 256*256*256*256*256+101;
+-------------------------+
| 256*256*256*256*256+101 |
+-------------------------+
| 1099511627877 |
+-------------------------+
1 row in set (0.00 sec)
mysql> select last_insert_id();
+------------------+
| LAST_INSERT_ID() |
+------------------+
| 1099511627877 |
+------------------+
1 row in set (0.00 sec)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1090 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAd2pFfFLsDUXQAIFT692EYTvRoaJmJoks5sNqMGgaJpZM4OXSCT>
.
--
----------------------------------
John Breen
Manager Production Systems | DialogTech
866.879.8912 | [email protected]
www.dialogtech.com | Twitter <http://twitter.com/dialogtech> | Facebook
<http://facebook.com/dialogtech>
We're proud to be a Crain's Best Place to Work
<http://www.chicagobusiness.com/section/best-places-to-work>!
|
Thank you for the report. |
Fixed in 1.3.9 and 1.4.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MySQL environment innodb_version = 5.6.32-78.0
ProxySQL version 1.3.7
Our auto_increment columns are BIGINT values.
One table has definitely already cleared the 32 bit max value..
The following code is hitting ProxySQL...
INSERT INTO
usr_activity
(activity_id
,user_id
,acct_id
,sid
,start_time
,activity_type
,usr_activity_type_id
,activity_query
,caller_id
,ref_data_1
,ref_data_2
,ref_data_3
,ref_data_4
,ref_data_5
) VALUES (NULL, '0', '917', 'james', CURRENT_TIMESTAMP, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL);SELECT LAST_INSERT_ID();
values returned when hitting proxySQL
1915171621 -> 0x72273325
when bypassing proxySQL and executing the same two queries, the returned values are ....
1234570785583 -> 0x11F7227332F (auto_increment_increment = 10)
Which is a BIGINT 64 number ...
The text was updated successfully, but these errors were encountered: