https://www.percona.com/blog/pt-archiver-with-auto-increment-column Fri, 22 Apr 2022 09:46:23 +0000 hourly 1 https://wordpress.org/?v=6.5.2 https://www.percona.com/blog/pt-archiver-with-auto-increment-column/#comment-10973598 Fri, 22 Apr 2022 09:46:23 +0000 https://www.percona.com/blog/?p=80733#comment-10973598 For me, I would to get all rows matching my query, that’s why my confusion =), Thanks Kedar, for this explanation ! When I made this test I should try to keep some data, but it’s was more simple to check that all tables were empties.

]]> https://www.percona.com/blog/pt-archiver-with-auto-increment-column/#comment-10973596 Thu, 21 Apr 2022 16:23:39 +0000 https://www.percona.com/blog/?p=80733#comment-10973596 I am the author of mentioned topic :p, I will try again with newest version =)

]]> https://www.percona.com/blog/pt-archiver-with-auto-increment-column/#comment-10973593 Tue, 19 Apr 2022 19:43:30 +0000 https://www.percona.com/blog/?p=80733#comment-10973593 My preferred behavior in this case would be (a) don’t delete the row with the max auto-increment value from the original table, (b) but do copy it to the other table anyway. That way, if you recreated the original table using the data from the archive table, you’d have all the data. If you kept using the original table, the auto-increment value would keep ascending. And if you copied more data from that same table to the archive table in the future, you would just get 1 row rejected due to a duplicate key.

]]>