Allowing user-generated strings to appear in the fastcat table has two problems:
They can take up enormous amounts of memory (this greatly confused the NYTworm, and will eventually make OneClick hosted infrastructure unsustainable.)
GROUP BY queries take much longer. (For example, to return the results for each result in ChronAm takes 8 seconds with a character element of about 12, as opposed to about 3 seconds with a MEDIUMINT variable.
This will require significantly rejiggering the code, though, particularly on the API end to have some subqueries at the end to apply the longer names back transparently.
Allowing user-generated strings to appear in the fastcat table has two problems:
This will require significantly rejiggering the code, though, particularly on the API end to have some subqueries at the end to apply the longer names back transparently.