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

Support for longer terms #95

Open
JonasR- opened this issue Dec 16, 2019 · 1 comment
Open

Support for longer terms #95

JonasR- opened this issue Dec 16, 2019 · 1 comment
Labels
feature Feature request

Comments

@JonasR-
Copy link

JonasR- commented Dec 16, 2019

Is your feature request related to a problem? Please describe.
I am currently trying to translate a application. There are tons of larger term e.g. email templates or pdf templates which have to be translated.
At the moment I cant import them into traduora as the terms are to long for the DB field.
From what I found out is that the value field in the terms table cant grow in size because of the index which is required for the unique.

Describe the solution you'd like
Maybe a hash can be generated from the term value which is then used for the unique. With this solution we might be able to have larger terms.

@JonasR- JonasR- added the feature Feature request label Dec 16, 2019
@JonasR-
Copy link
Author

JonasR- commented Dec 16, 2019

I just tried my idea.
I created a new column for the hash and two trigger which are creating the hash on insert and update. Also I changed the term value type to MEDIUMTEXT and changed the index.

It works if I add/change a term over the database but I cant do it over the webinterface.

phrobix pushed a commit to phrobix/traduora that referenced this issue Jun 4, 2020
Made the values column type in sync with the values colum of the translations

issue: ever-co#95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request
Projects
None yet
Development

No branches or pull requests

1 participant