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
The current schema allows to insert values for the current Identity properties: source, email, name and username that due to their length are truncated to fit in the fields of the identities table. This is possible in DBMS like MySQL when STRICT_TRANS_TABLES or similar kind of parameters are not set.
There are two reasons to forbid this behaviour:
The values in the tables are different to those the user wanted to store
The UUID of the identity is invalid. Currently, the id of an identity is generated using the original values given by the user and not using the truncated values. This means the generated ID is wrong for a identity which its properties were truncated and we cannot recover the ID of one of these identities using the tuple (source, email, name, username).
The current schema allows to insert values for the current
Identity
properties:source
,email
,name
andusername
that due to their length are truncated to fit in the fields of theidentities
table. This is possible in DBMS like MySQL whenSTRICT_TRANS_TABLES
or similar kind of parameters are not set.There are two reasons to forbid this behaviour:
Issue related #67
The text was updated successfully, but these errors were encountered: