The sql is generated in the expression class of the the plugin for
your db.
You could for example generate the expression, get the statement, fix
it and put it into the fetch spec as a hint, probably in a DBC
delegate. Or you could write your own plugin by subclassing the
oracle plugin and override
public String assembleSelectStatementWithAttributes(NSArray
attributes,
boolean lock,
EOQualifier
qualifier,
NSArray
fetchOrder,
String
selectString,
String
columnList,
String
tableList,
String
whereClause,
String
joinClause,
String
orderByClause,
String
lockClause) {
Cheers, Anjo
Am 28.03.2006 um 05:47 schrieb David Sargent:
The question is how is the best way to get WO to allow me to use
this oracle feature. I looked at overriding the EOSortOrdering to
create my own. Not clear on where the SQL is generated. Any
suggestions would be appreciated. I have too many records to do it
internally. I have looked at doing rawRowsForSQL and then convert
the objects to EO. That solution will cause me some problems in
another area. Any other suggestion would be very much appreciated.
_______________________________________________
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]
