We should not try to make this work on Oracle since it's simply a very bad thing to do in general. Instead, we should fix all places where we try to sort/filter on large strings (either by not doing it anymore, or by refactoring the field to not be a large string).
Thomas Mortagne on 13/Aug/25 11:13
We should not try to make this work on Oracle since it's simply a very bad thing to do in general (sorting/filtering on a not indexed column will take forever if the document table is big). Instead, we should fix all places where we try to sort/filter on large strings (either by not doing it anymore, or by refactoring the field to not be a large string).
Thomas Mortagne on 13/Aug/25 11:15
We should not try to make this work on Oracle since it's simply a very bad thing to do in general (sorting/filtering on a not indexed column will take forever if the document table is big). Instead, we should fix all places where we try to sort/filter on large strings (either by not doing it anymore, or by refactoring the field to not be a large string, for example the way we store list of users/groups right now does not make any sense and we should probably introduce a new type of property for user and groups which does things properly).
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
