diff options
author | Bryan Newbold <bnewbold@robocracy.org> | 2018-09-15 17:00:10 -0700 |
---|---|---|
committer | Bryan Newbold <bnewbold@robocracy.org> | 2018-09-15 17:00:12 -0700 |
commit | be3a4333c5880f3af1a4e6adbba31a030a5ebc72 (patch) | |
tree | 68bfbab3a56a61b5370aebb640ab807db9da8163 /extra/extid_map | |
parent | a11ee8d8c0fd1f924d7ba7feec58cd3fcf28752b (diff) | |
download | fatcat-be3a4333c5880f3af1a4e6adbba31a030a5ebc72.tar.gz fatcat-be3a4333c5880f3af1a4e6adbba31a030a5ebc72.zip |
update extid columns: varchar size limits, no char columns
In PostgreSQL, there is no query or size differences between CHAR,
VARCHAR, and TEXT: they use the same backend. CHAR will pad out with
spaces and VARCHAR enforces a size limit.
The enforced VARCHAR size limit seems like ok defensive
programming/schema here, preventing large values from getting stored for
some columns. I have some FUD concern about fixed-sized identifiers and
indexes, so switching old CHARs (eg, sha1 hex encoded columns) to
VARCHAR instead.
Diffstat (limited to 'extra/extid_map')
0 files changed, 0 insertions, 0 deletions