Any advice?
That it the way it is. I don't know how easy it would be to
optimize these. EOF might expect there to be only a single entity
per result set.
I was pretty sure I was not seeing this behavior, so I verified it in
one of our apps:
to-many fault:
2008-02-07 16:14:27,535 DEBUG 17.9 MB/12.1 MB [WorkerThread1]
extensions.ERXNSLogLog4jBridge - evaluateExpression:
<com.webobjects.jdbcadaptor.FrontbasePlugIn$FrontbaseExpression:
"SELECT t0."cellTypeID", <snip> FROM "SheetCell" t0 WHERE
(t0."cellTypeID" IN (1, 6, 4, 3, 2, 5) AND t0."rowID" = 1005629)">
top-level fetch:
2008-02-07 16:16:27,450 DEBUG 30.14 MB/3.26 MB [WorkerThread8]
extensions.ERXNSLogLog4jBridge - evaluateExpression:
<com.webobjects.jdbcadaptor.FrontbasePlugIn$FrontbaseExpression:
"SELECT t0."cellTypeID", <snip> FROM "SheetCell" t0 WHERE
(t0."cellTypeID" IN (1, 6, 4, 3, 2, 5) AND t0."maxSlots" = 5)">
So it's not definitely not doing this. I tried with an abstract and
non-abstract super-entity here, and got the same results.
I checked another app and tried a polymorphic to-one fault:
Feb 07 16:27:50 MDTask[60756] (ERXNSLogLog4jBridge.java:44) DEBUG
NSLog - evaluateExpression:
<com.webobjects.jdbcadaptor.FrontbasePlugIn$FrontbaseExpression:
"SELECT <snip> t0."RequestTypeNumber" <snipagain> FROM "Request" t0
WHERE (t0."RequestTypeNumber" IN (1, 2, 3) AND t0."RequestID" =
1006678)">
It's possible that Wonder fixes this, but I don't think I wrote that
if it does ... I'll look through the code some. Can anyone not using
Wonder verify this?
ms
_______________________________________________
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]
