Just to say, because it's a standard JDBC feature I don't think that letting
the user set this param can do much harm. Nevertheless, I perfectly
understand that you can't take any change lightly.
In fact most other OR tools let you set this param. In Ibatis you can do it
directly in your query mapping file. Hibernate criteria queries have a
setFetchSize() method and, looking for similar issues on the Jira I found
something like this concerning OJB. Don't get me wrong, I'm not trying to
say that it's a shame or anything negative, just sharing what I could learn
elsewhere on this topic.
I try to avoid this as much as possible but I think I'm going to make this
change myself so I can begin working on my project while you do all the
required testing. I really like cayenne and I have seen that there's a nice
community that kindly answers your questions without trying to make you feel
like an idiot.
Thanks everyone...
Andrus Adamchik wrote:
>
> Thanks for the Jira. Can't give you a time estimate on that, we are an
> open source project after all. All I can say now is that adding this
> API to Cayenne is fairly trivial (you can even take a shot at this
> yourself, if you feel like hacking the Cayenne internals). But before
> we commit anything like that, I'd like us to research the effects of
> this on at least a few of the databases that Cayenne supports, and
> various driver-specific caveats that I am sure will arise. So this
> will take some time to make it a production quality feature.
>
> Andrus
>
>
-- View this message in context: http://www.nabble.com/Big-selects-on-PostGres-%3A-Configuring-Statement.setFetchSize%28%29-of-a-selectquery-tp23555842p23586272.html Sent from the Cayenne - User mailing list archive at Nabble.com.
This archive was generated by hypermail 2.0.0 : Sun May 17 2009 - 14:36:08 EDT