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
PostgresSQL's bigint data type is currently used for all ids in all databases. Those ids are nearly everywhere mapped to number in TS/JS, which is problematic because bigint is a 64-bit integer value whereas number is only a 53-bit integer value.
As discussed with @georg-schwarz and @mathiaszinnen it is desired that the type of those numeric ids should be changed to strings, to solve this issue. Users should then also able to chose their own speaking names for the ids, so they can more easily remember and work with them.
The text was updated successfully, but these errors were encountered:
PostgresSQL's
bigint
data type is currently used for all ids in all databases. Those ids are nearly everywhere mapped tonumber
in TS/JS, which is problematic becausebigint
is a 64-bit integer value whereasnumber
is only a 53-bit integer value.As discussed with @georg-schwarz and @mathiaszinnen it is desired that the type of those numeric ids should be changed to strings, to solve this issue. Users should then also able to chose their own speaking names for the ids, so they can more easily remember and work with them.
The text was updated successfully, but these errors were encountered: