Actually .. Should be pretty easy to replace _OrQualifierSupport with
an impl that checks that if your OrQualifier consists of only
EOKeyValueQualifiers where the key is the same and the selector is
"equals" then swap out sql gen for an in set, otherwise just pass on
to the default impl.
On Dec 2, 2006, at 11:15 PM, Mark Ritchie wrote:
Hi Mike!
On 2-Dec-06, at 11:45 AM, Mike Schrag wrote:
But just so I don't make batchFetchRelationship's head too big, it
is still EOF, so it will make an enormous EOOrQualifier of the
companies rather than a slightly nicer In-Set qualifier.
IIRC, that's because batchFetchRelationship dates to the Obj-C days
and the in-set operator wasn't as commonly supported by databases
then as it is today. The massive use of 'or' statements has
sometimes caused me grief when there are a lot of join conditions
and the length of the SQL statement exceeds what the database can
handle. The use of an in-set operator would help in that specific
case. Overall, I'm not sure if an in-set operator would be any
faster then 'or' statements. In fact, IIRC some databases convert
the in-set operator to 'or' statements before evaluation anyways.
Regards,
Mark
__
Mark Ritchie
Toronto Ontario Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag%
40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
