-
Notifications
You must be signed in to change notification settings - Fork 123
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
Better types for table columns (VARCHAR instead of TEXT) #824
Comments
any progress on it? Looks like the same issue produces lots of tracebacks during bootstrapping of srcd-ce (which don't break anything but annoying). |
Some, but I paused it when transferred to solutions, since it's giving problems I'll retake it tomorrow. |
Looks like not all of them produced by TEXT fields but the most anyway. |
Grepping, sorting, and uniq-ing the types on that log for easier reading:
|
Currently query
produces
Which is technically correct but columns like
repository_id
,commit_hash
,commit_author_name
, ... better beVARCHAR
By semantic TEXT mean huge chunk of text and due to it unique. While
VARCHAR
holds reasonable amount of text and often repeats.No wonder people rely on it. For example Superset makes columns gropable and filterable when they are
VARCHAR
but doesn't do it forTEXT
.Source{d} product has a bug because of it. And it might be useful in some other use cases too.
The text was updated successfully, but these errors were encountered: