Figured I'd resend the message to this list to get more feedback. Do
many people find this API useful?
My main motivation for removal of this API is to reduce confusion. It
overlaps with query caching and the subtle difference between
"setRefreshingObjects" and "setCachePolicy" is unclear to many users.
At the same time the later does not *directly* replace the former, and
I can see how under some very special circumstances
"setRefreshingObjects(false)" could yield marginally better
performance (e.g. a set of queries with a large # of combinations of
parameters, but all searching the same underlying data set that rarely
changes), but IMO that does not justify the confusion it leaves...
So I guess a more specific question is - does anyone's application
heavily rely on this optimization and will suffer if we get rid of it
in the sake of better clarity?
Andrus
Begin forwarded message:
From: Andrus Adamchik <[EMAIL PROTECTED]>
Date: April 18, 2008 12:02:27 AM GMT+03:00
To: [EMAIL PROTECTED]
Subject: Query.setRefreshingObjects(boolean)
Reply-To: [EMAIL PROTECTED]
Anyone's using "SomeQuery.setRefreshingObjects(false)"?
I haven't been using this since WebObjects days, and with all the
Cayenne query cache/refresh options, don't find a need for it at
all. Any objections to deprecating this parameter and actually
ignoring it in runtime?
(BTW, this was brought up before, but never acted upon:)
http://objectstyle.org/cayenne/lists/cayenne-devel/2006/02/0073.html
Andrus
