Page MenuHomePhabricator

Support AUTO_INCREMENT in `bin/storage adjust`
ClosedPublic

Authored by epriestley on Sep 29 2014, 7:17 PM.
Tags
None
Referenced Files
F15521695: D10607.diff
Sun, Apr 20, 3:40 PM
F15514335: D10607.id25449.diff
Fri, Apr 18, 2:05 AM
F15513275: D10607.id.diff
Thu, Apr 17, 5:43 PM
F15509393: D10607.diff
Wed, Apr 16, 12:06 PM
F15484488: D10607.id25477.diff
Wed, Apr 9, 6:32 PM
F15426089: D10607.id25477.diff
Mar 23 2025, 7:00 AM
F15418057: D10607.diff
Mar 20 2025, 8:29 PM
F15403293: D10607.diff
Mar 18 2025, 2:39 AM
Subscribers

Details

Summary

Ref T1191. When changing the column type of an AUTO_INCREMENT column, we currently may lose the autoincrement attribute.

Instead, support it. This is a bit messy because AUTO_INCREMENT columns interact with PRIMARY KEY columns (tables may only have one AUTO_INCREMENT column, and it must be a primary key). We need to migrate in more phases to avoid this issue.

Introduce new auto and auto64 types to represent autoincrement IDs.

Test Plan
  • Saw autoincrement show up correctly in web UI.
  • Fixed an autoincrement issue on the XHProf storage table with bin/storage adjust safely.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Support AUTO_INCREMENT in `bin/storage adjust`.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Sep 30 2014, 5:08 PM
This revision was automatically updated to reflect the committed changes.