Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems storing truncated strings for Identity properties #68

Open
sduenas opened this issue Jun 9, 2016 · 0 comments
Open

Problems storing truncated strings for Identity properties #68

sduenas opened this issue Jun 9, 2016 · 0 comments
Labels

Comments

@sduenas
Copy link
Member

sduenas commented Jun 9, 2016

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:

  1. The values in the tables are different to those the user wanted to store
  2. 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).

Issue related #67

@sduenas sduenas added the bug label Jun 9, 2016
valeriocos pushed a commit to valeriocos/grimoirelab-sortinghat that referenced this issue Jun 18, 2018
T1376: Script to recover tweets from Twitter Search API

LGTM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant