ltu_phrases.key as varchar causes problems with long keys commonly used in JSON files

[philippgerard]

Hi,

I'm using long keys for some translated marketing pages, e.g. T&Cs, Privacy Policy etc. When importing the strings from the JSON files the import fails with "data too long for column 'key'". Turning the key into text from varchar fixes the problem and might be worth considering as a default.

Thanks for the great package otherwise!

Best, Philipp