Hi there,
I saw some strange result when I use some code like this:
someMagmaCollection where:[:reader| reader read: #companyName to:'ZZZ'] distinct: true sortBy: #companyName descending: false.
then the result of that is used like:
queryResult copyFrom: firstDesiredItemOfResult to: lastDesiredItemOfResult
this last message is returning instantaneusly an empty array when in fact should not be empty. And seems to be only for the first send because if I resend the message, for instance manually in the debugger, I do get the right results for the next N (re)sends.
How is expected to reach the result when you ask for it waiting for it if necessary?
cheers,
Sebastian Sastre
Hi Sebastian, this is explained in the documentation here:
http://wiki.squeak.org/squeak/5859
under the heading "Sorting".
On 10/31/07, Sebastian Sastre ssastre@seaswork.com wrote:
Hi there,
I saw some strange result when I use some code like this:
someMagmaCollection where:[:reader| reader read: #companyName to:'ZZZ'] distinct: true sortBy: #companyName descending: false.
then the result of that is used like:
queryResult copyFrom: firstDesiredItemOfResult to: lastDesiredItemOfResult
this last message is returning instantaneusly an empty array when in fact should not be empty. And seems to be only for the first send because if I resend the message, for instance manually in the debugger, I do get the right results for the next N (re)sends.
How is expected to reach the result when you ask for it waiting for it
if necessary?
cheers,
Sebastian Sastre
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
magma@lists.squeakfoundation.org