tag:blogger.com,1999:blog-18725506.post4225822395766194977..comments2010-02-11T15:40:17.420+05:30Jang Vijay Singhhttp://www.blogger.com/profile/11926334117288628075noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-18725506.post-62741167396547748242010-02-11T15:40:17.420+05:302010-02-11T15:40:17.420+05:30Many thanks, John and Chris. <br />I really have no valid excuse for not responding earlier. <br />The example you&#39;ve mentioned is surely not declaratively achievable (like the other cases listed in the developer guide that need expert mode hand-coded SQL)<br /><br />On the caches, I fould this informative list by Chris:<br />http://forums.oracle.com/forums/thread.jspa?messageID=4090407&amp;#4090407Jang Vijay Singhhttp://www.blogger.com/profile/11926334117288628075noreply@blogger.comtag:blogger.com,1999:blog-18725506.post-65024462235878976842010-02-08T22:59:11.302+05:302010-02-08T22:59:11.302+05:30I thought that VOs have their own cache, and don&#39;t depend on an EO to cache data. Some of my read-only VOs are based on read-only database objects, like non-updatable views, or SELECT FROM TABLE(function_returning_table). Some SHOULD be re-queried every time they are used, because the underlying data changes frequently.JCFlackhttp://www.blogger.com/profile/07116756139055371171noreply@blogger.comtag:blogger.com,1999:blog-18725506.post-41168965213538793482010-02-08T06:38:06.976+05:302010-02-08T06:38:06.976+05:30Nice post Jang with thanks.<br /><br />CM.Chris Muirhttp://www.blogger.com/profile/06566648350240654621noreply@blogger.com