Commit 9566abf
Change ordering_key column from VARCHAR(512) to TEXT
ordering_key is an arbitrary string (often a URL in Fedify), so the
previous VARCHAR(512) limit could silently truncate or reject values
longer than 512 characters at insert time with an opaque DB error.
Switch the column to TEXT so there is no fixed-length cap. Because
InnoDB requires a prefix length when indexing TEXT columns, the
composite index now uses ordering_key(766):
766 chars * 4 bytes (utf8mb4) + 8 bytes (DATETIME(6)) = 3072 bytes
which exactly hits InnoDB's 3072-byte key limit.
Existing tables created with the old VARCHAR(512) definition will
continue to work; operators who want to lift the 512-char cap must
ALTER the column manually (or drop and recreate the table via drop()).
#599 (comment)
Co-Authored-By: claude-sonnet-4-6 <claude-sonnet-4-6@anthropic.com>1 parent 6c67e95 commit 9566abf
1 file changed
Lines changed: 10 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
539 | 539 | | |
540 | 540 | | |
541 | 541 | | |
542 | | - | |
543 | | - | |
544 | | - | |
545 | | - | |
| 542 | + | |
| 543 | + | |
| 544 | + | |
| 545 | + | |
546 | 546 | | |
547 | 547 | | |
548 | 548 | | |
| |||
558 | 558 | | |
559 | 559 | | |
560 | 560 | | |
| 561 | + | |
| 562 | + | |
| 563 | + | |
| 564 | + | |
| 565 | + | |
561 | 566 | | |
562 | 567 | | |
563 | | - | |
| 568 | + | |
564 | 569 | | |
565 | 570 | | |
566 | 571 | | |
| |||
0 commit comments