TiDB implements the AUTO_INCREMENT implicit assignment in the following way:įor each auto-increment column, a globally visible key-value pair is used to record the maximum ID that has been assigned. However, in terms of the specific value that is implicitly assigned, TiDB differs from MySQL significantly. The usage above is the same as that of AUTO_INCREMENT in MySQL.

In such cases, TiDB stores the explicitly specified values: INSERT INTO t(id, c) VALUES (6, 6) In addition, AUTO_INCREMENT also supports the INSERT statements that explicitly specify column values. The following is a basic example of AUTO_INCREMENT: CREATE TABLE t(id int PRIMARY KEY AUTO_INCREMENT, c int)

On the other hand, this step is only needed if I add new games via product-keys or steam-gifts.If you want the AUTO_INCREMENT numbers to be monotonic on all TiDB servers and your TiDB version is v6.5.0 or later, it is recommended to enable the MySQL compatibility mode. So for every account you have to make 1 AJAX-Request and this way I can’t cut it down to your example.

The problem here is, I have to be 100% sure a certain account owns a specific game and the other problem is, you can only get the “Owned Games” of one account via API. There’s a Steam-API where you can get the “owned games” of every Steam-Account. I’m having several Steam-Accounts and every account has some games in it. I could only give you an example what I really want to achieve and maybe it’s more understandable for you. Also and this isn´t against you, if you use Vanilla IDB-commands this problem doesn’t occur and thats why I’m asking if we have to investigate this further. Hm, I can´t find out why it is so slow with an open console, but I will have a look at your code when I have more time.

Reset mysql quot increment