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
A few times, we've had to empty our easyaudit tables due to the amount of data we added because they were failing to insert due to running out of primary keys.
Update the primary_key to a BigInt would help with this
The text was updated successfully, but these errors were encountered:
Just adding a note to the person who ends up implementing this:
In the release notes for this change include information about how Django applies this in migrations. Doing a sqlmigrate on a migration file where the field changes the workflow is:
Create new table with same columns
Insert all existing data into this table
Drop existing table
Rename new table
Recreate indexes.
Given how much data is could be coming into these tables, any custom indexes, or partitions in the DB, the effect of a change like this needs some big warning lights in the release notes, given that this amount of IO could potentially bring the DB offline to users.
A few times, we've had to empty our easyaudit tables due to the amount of data we added because they were failing to insert due to running out of primary keys.
Update the primary_key to a BigInt would help with this
The text was updated successfully, but these errors were encountered: