|
|
Hi,
imho you should not rely on priority analysis of a method that does text parsing for creating proper SQL (I would assume the brackets are set by order not by operator?). If you need priority brackets either set them yourself in your qualifier string or use the EOAndQualifer and EOOrQualifier classes.
Best regards,
Susanne
Am 15.02.2021 um 14:47 schrieb OCsite:
Hi there,
is it normal that
EOQualifier.qualifierWithQualifierFormat("userType = 12 OR userType = 6 AND subjectType = 3",null)
creates
*(((userType = 12) or (userType = 6)) and (subjectType = 3))*
? Seems wrong, does it not? /AND/ should always have higher operator precedence than /OR/, should it not? I was just bit in my tender parts by this, and I wonder whether this is the standard behaviour or some weird quirk.
Thanks,
OC
--
Susanne Schneider
Coordinator secuTrial® Development
interActive Systems GmbH
Glogauer Str. 19, D-10999 Berlin
fon +49 30 22 50 50 - 498
fax +49 30 22 50 50 - 451
mail susanne.schneider@interActive-Systems.de
web http://www.secuTrial.de
----------------------------------------------------
Geschäftsführer: Dr. Marko Reschke, Thomas Fritzsche
Sitz der Gesellschaft: Berlin
Amtsgericht Berlin Charlottenburg, HRB 106103B
----------------------------------------------------
|
|