|
-
Uh, not that I'm aware of, and certainly not to an extent that it would invalidate the *multiple* advantages that use of an abstraction layer (in PL/SQL) enables. In PL/SQL, if you simply open a RefCur with the large SQL statement and return that to the calling proc, you have done practically nothing in PL/SQL *except* to keep the calling program from containing SQL, which has immense value. The overhead is extremely minimal. Now, if you *do* have an abstraction layer, the potential performance benefits that can be realized down the road can be enormous and certainly eclipse any minor overhead realized now.
Now, if you are using table parameters, your overhead will definitely be larger, but that's why one doesn't use table parameters any more. *Even if* you are still using table parameters to return result sets, the benefits of an abstraction layer still far outweigh the minor overhead incurred.
- Chris
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|