EZP-26277: Content type copies generated identifiers are too long #1791
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR shortens generated identifiers of content type copies.
Instead of:
copy_of_<identifier>_<remoteId>
now we have:
cpy_<identifier>_<remoteId>
Also,
<remoteId>
is no longer amd5
hash but asha1
hash shortened to 7 chars. We can't get rid of<remoteId>
in copied content type identifier because it would be impossible to copy content type several times.Another possible approaches:
varchar
varies between DBMS-es and should be tested on large databases (about 2 mln of Content Objects).6.x
(IMHO).TODO