Hi,
In the glorp guide I can read:
The second restriction on a query block concerns the messages that may be sent to instance variables inside the block. These messages include:
Binary operators: <, >, =, ~=, >=, <=, <>
like:
isNIL, notNIL
-
AND:, &, OR:, |
Methods in the API protocol of class ObjectExpression
Now...imagine a place in my app, that sends a readManyOf:. THis place is called with a class and a blockclosure. There are several senders. Some may be fine as a blockclosure for the where: argument, but some may not. So on the first hand, I am able to use the selector with the where: but with the second case, I have to do the readManyOf: alone and then filter/select in memory.
So my question is, did someone already wrote a helper method in BLockClosure say #glorpIsSuitableForWhereArgument that answers where a BlockClosure is ok or not to work as an argument to where: ?
--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To post to this group, send email to
[hidden email].
Visit this group at
http://groups.google.com/group/glorp-group.
For more options, visit
https://groups.google.com/groups/opt_out.
Locked
