tag:blogger.com,1999:blog-4818542164384221282.post8325456154623138723..comments2012-01-25T12:36:23.451+08:00Scott Wesleyhttps://profiles.google.com/116811643017542807963noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-4818542164384221282.post-48291812883462138512012-01-25T12:36:23.451+08:002012-01-25T12:36:23.451+08:00Indeed Mohan, passing parameters to pl/sql modules is a good practice for a number of reasons. <br /><br />Good to hear you obtain so much performance benefit out of it.Scott Wesleyhttp://www.blogger.com/profile/18106937181788036683noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-80386891928670600092012-01-24T01:24:31.932+08:002012-01-24T01:24:31.932+08:00I agree with Buzz Killington. I practically experienced tremendous performance improvement using package/procedures/functions and passing as parameters.Mohannoreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-31917819467629819292012-01-12T10:19:12.433+08:002012-01-12T10:19:12.433+08:00Hi Luis, I had a great new year, cheers.<br /><br />That&#39;s a really good example of when to use v() - I&#39;ve done that myself, quite possibly at your site! <br />That forum entry is a good one, I&#39;ve been meaning to look into that behaviour myself.Scott Wesleyhttp://www.blogger.com/profile/18106937181788036683noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-72250296694195925922012-01-12T10:02:42.792+08:002012-01-12T10:02:42.792+08:00Hi Wesley<br /><br />How are things going? Nice post!<br /><br />I think that the only cases where you need to use the v() function inside Apex are when you are generating the session item name dynamically and don&#39;t have at compile time the name of the item (e.g. v(&#39;P10_CODE&#39;||i)) or a workaround for this bug (although it seems that it is only me who consider it a bug!):<br /><br />https://forums.oracle.com/forums/thread.jspa?messageID=9930990<br /><br />Other than that, I don&#39;t see a need to use v(), specially in queries.<br /><br />Cheers,<br />LuisLuishttp://www.blogger.com/profile/10801377551877341826noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-76207193865275024472012-01-12T09:24:23.020+08:002012-01-12T09:24:23.020+08:00But I think the question is, do we ever need to use the v() function?<br /><br />If we pass actual parameters as bind variables to our pl/sql, and we use bind variables in the apex queries and conditions - the need for deterministic wrappers may be mute.<br /><br />So is there ever a <i>need</i> to use v() ?Scott Wesleyhttp://www.blogger.com/profile/18106937181788036683noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-43581926529822114202012-01-11T23:36:23.722+08:002012-01-11T23:36:23.722+08:00Hi,<br />I agree that parameters are the best solution but if you need/want to use v() function than you can read this link:<br />http://www.inside-oracle-apex.com/caution-when-using-plsql-functions-in-sql-statement/<br /><br />If you decide to use wrapper deterministic function then don&#39;t forget that you have to upgrade your wrapper with each APEX upgrade.<br /><br /> LevUnknownhttp://www.blogger.com/profile/07738586409100836666noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-25173995883948631042012-01-11T23:04:39.709+08:002012-01-11T23:04:39.709+08:00Good point, buzz. I was so focused on the bind variable issue, I forgot about that.<br /><br />I&#39;ve found so much value in sending them as parameters - makes testing &amp; debugging so much easier.Scott Wesleyhttp://www.blogger.com/profile/18106937181788036683noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-17923384576882184122012-01-11T22:14:28.464+08:002012-01-11T22:14:28.464+08:00I still think the best practice is to use packages/procedures/function and pass everything in as parameters. Then you don&#39;t have a need to use v(). Not saying you&#39;ll never need v(), but it cuts down on its usage a bunchBuzz Killingtonnoreply@blogger.com