Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
2.0.1
-
None
-
migration
-
Hard
-
Description
This is mostly invisible to the user, and only creates a problem when the user tries to query StringListProperties and LargeStringProperties in the same query. It requires a messy workaround for the new document loader and fixing it will eliminate any technical need for storing BaseProperty.classType
I am putting it here so that it may be changed in the next database migration.
Example of a user query which will fail due to this limitation:
{{groovy}}
try{
xcontext.getContext().getWiki().search("select prop1, prop2 from IntegerProperty prop1, StringProperty prop2", xcontext.getContext());
}catch(Exception e){println("The control test failed.");return;}
println("Selecting IntegerProperty and StringProperty succeeds.\n");
try{
xcontext.getContext().getWiki().search("select prop1, prop2 from LargeStringProperty prop1, StringListProperty prop2", xcontext.getContext());
}catch(Exception e){println("Selecting LargeStringProperty and StringListProperty fails.");}
{{/groovy}}