Future fix xf_thread_read auto_increment out of range

There is actually a blocker to correctly supporting ip_id being 64bit (technically any other ids, but most of them aren't written to like ip_id is).

XF\Mvc\Entity\ValueFormatter::applyValueConstraints assumes 32bits integers not 64bit integers

This can be worked around by adding 'max' => \PHP_INT_MAX to the ip_id column definition.
 
Last edited:
With mariaDB's Galera Clustering (and custom alerting), SpaceBattles.com has recently has reached more than 2^32 for the alert_id column
 
Last edited:
Automated triage: Future fix

Thank you for reporting this issue. The thread read ID column is still a standard unsigned integer in the current version, so a very busy site with a large auto-increment step can eventually run out of IDs. Changing it means a schema change on a very large table, so this is kept open as a longer-term change. Changing the column to BIGINT yourself is still a safe workaround.

This is an automated assessment. A member of staff may review and update it.
 
Back
Top Bottom