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
There's no information about a limit of a number of columns and indexes in Starcounter, but some people already hit these. This should be explicitly said in appropriate places in the database section of the documentation.
Limit of number of columns: 127 (should be checked with core team)
Limit of number of indexes per table: 32 (but it is a bit more complicated than that because of inheritance and implicitly created indexes). Should be precisely checked.
The text was updated successfully, but these errors were encountered:
Additional info: First one is a limit of 31 (actually 32, but 1 is used internally) indexes per type. And indexes from base types also count to this cap.
Second one is a total limit of 64K indexes per database. And this is the one 'ScErrIndexLimitReachedAbort' indicates. Most likely they just abandoned a lot of tables and indexes over the database lifetime and haven't actually dropped abandoned tables. Or we have some
There's no information about a limit of a number of columns and indexes in Starcounter, but some people already hit these. This should be explicitly said in appropriate places in the database section of the documentation.
Limit of number of columns: 127 (should be checked with core team)
Limit of number of indexes per table: 32 (but it is a bit more complicated than that because of inheritance and implicitly created indexes). Should be precisely checked.
The text was updated successfully, but these errors were encountered: