last_insert_id gives 0 when 0 is explicitly specified for an auto_increment primary key in an insertion

[ko41]

As is described in this example,

https://github.com/dolthub/go-mysql-server/blob/729f39b6b665932cb0da516d5013f0d938c860d0/enginetest/queries/insert_queries.go#L559-L567

When 0 is specified explicitly,

• a new row with id 4 is created,
• but we have 0 as InsertID.

This is not consistent with MySQL's behaviour, which can be replicated as follows:

> docker run -e MYSQL_ROOT_PASSWORD=root -e MYSQL_DATABASE=test -p 3306:3306 -d mysql:8
> mysql -h 127.0.0.1 -P 3306 -u root -p'root' test

MySQL [test]> CREATE TABLE `auto_increment_tbl` (   `pk` bigint NOT NULL AUTO_INCREMENT,   `c0` bigint,   PRIMARY KEY (`pk`) );
Query OK, 0 rows affected (0.016 sec)

MySQL [test]> INSERT INTO auto_increment_tbl values (0, 44);
Query OK, 1 row affected (0.031 sec)

MySQL [test]> select last_insert_id();
+------------------+
| last_insert_id() |
+------------------+
|                1 |
+------------------+
1 row in set (0.001 sec)

MySQL [test]> SELECT * FROM auto_increment_tbl ORDER BY pk;
+----+------+
| pk | c0   |
+----+------+
|  1 |   44 |
+----+------+
1 row in set (0.001 sec)

[fulghum]

Hi @ko41, thanks for taking the time to report this discrepancy with MySQL's behavior. I've moved this issue over to the dolt repository so that it'll get more attention from our team (even though the fix will likely involve changes in go-mysql-server).

I am able to reproduce the behavior you're reporting with last_insert_id() – if 0 is provided for the auto_increment column value, then MySQL will replace that with the next value in the auto_increment sequence. Dolt and GMS are doing that part correctly, but they are still reporting 0 when last_insert_id() is called, which is the incorrect behavior here.

Let me know if I misunderstood anything in there. We'll see if we can get someone to dig into this fix.

[fulghum]

Hi @ko41, thanks again for reporting this issue. 🙏 I've fixed the bug in the go-mysql-server package and I've merged the new dependency version into dolt, too. This will go out in the next Dolt release, next week. Just let us know if you need it released in Dolt faster and we'll be happy to kick off a release for you.

Let us know if you find any other issues!