You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
log_record.id is a signed INT, exhausted by applications logging a lot #294
log_record.id is a signed INT (#[ORM\Column(name: 'id')] on int, created as INT by the migrations): its maximum, 2 147 483 647, is reached in about 7 months by an application writing 10 million log records per day. The ids are not reused after a purge (auto-increment / identity): the insertion of the log records then fails.
Proposed fix
A BIGINT id for log_record (mapping and migration). The migration rebuilds a large table (and its foreign keys), and the type of LogRecord::getId() is unchanged in PHP but not in the database: for 4.0.
Requirements
Documentation updates
Reference
Cookbooks
Changelog
Unit tests
Breaking changes
A migration changing the type of log_record.id (long on large tables).
Activity