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
It seems as though it is possible for triple and possibly in the future access table to exceed the 2^31-1 limit for standard MySQL ints. It should be investigated whether existing tables can be altered to use bigint instead. This is certainly no bad idea for new archives but if a table reaches such a high ID it is liable to have a lot of records, so any alter table command is likely to take a long time and quite a lot of memory.
The text was updated successfully, but these errors were encountered:
It seems as though it is possible for triple and possibly in the future access table to exceed the 2^31-1 limit for standard MySQL ints. It should be investigated whether existing tables can be altered to use bigint instead. This is certainly no bad idea for new archives but if a table reaches such a high ID it is liable to have a lot of records, so any alter table command is likely to take a long time and quite a lot of memory.
The text was updated successfully, but these errors were encountered: