From: Mike S. <ms...@md...> - 2006-12-03 10:47:27
|
I just committed ERXInOrQualifierSupport (as discussed on webobjects- dev). If an EOOrQualifier passes through that has nothing but EOKeyValueQualifiers in it that all have the same key and that are all QualifierOperatorEquals, then it can generate an in-set query instead of a huge string of repetitive or-queries. Any other case and it just passes up to the standard implementation of _OrQualifierSupport. This is kind of a handy thing to have all the time, I think, so I'm wondering if anyone is opposed to this being registered as the default implementation of _OrQualifierSupport in ERXApplication? In the meantime, you can put the following into your application if you want to use it: EOQualifierSQLGeneration.Support.setSupportForClass(new ERXInOrQualifierSupport(), EOOrQualifier._CLASS); ms |