Niall Ross wrote:
Dear Herby,
adding #includesKey: is certainly doable. If you look at callers above
and subcallers below #anySatisfyDefault: you will see the issues
involved. Your includesKey: needs the same degree of platform-awareness
that Glorp's #anySatisfy: and #allSatisfy: implementations
jtuc...@objektfabrik.de wrote:
Herby,
I must admit I've never used Dictionary Mappings with Glorp, so I don't
have an answer.
But I am a bit confused by your code examples. See below
Am 24.10.17 um 20:27 schrieb Herby Vojčík:
Hello!
I am using a DictionaryMapping in my code, and I wanted to
Tom Robinson wrote:
Hi Herby,
In my opinion, the way you found to make it work is the way it should
be. The reason is that the first way doesn't translate into SQL and the
second one does. It might be possible to add includesKey: functionality
but resolving that to SQL would be more complex. I w
Herby,
I must admit I've never used Dictionary Mappings with Glorp, so I don't
have an answer.
But I am a bit confused by your code examples. See below
Am 24.10.17 um 20:27 schrieb Herby Vojčík:
Hello!
I am using a DictionaryMapping in my code, and I wanted to use
#includesKey: in #where:
Hello!
I am using a DictionaryMapping in my code, and I wanted to use
#includesKey: in #where: clause (something akin
each tools includesKey: aToolId
) to select only rows for which DictionaryMapping uses certain key. It
failed with the error in the lines of "#tools does not resolve to
fi
