Comments for Implicit Statement Results in Oracle Database 12c Release 1 (12.1) (DBMS_SQL.RETURN_RESULT and DBMS_SQL.GET_NEXT_RESULT)
Mark said...Thanks for the article. I can't help thinking that this dilutes the formality of the language and routine specification. Personally I hate side effects and if the code was wrapped, it wouldn't be obvious that a record set was being returned. Return values from a procedure? That should be a function!
I tend to agree with you. If you are an Oracle person you will probably never use it. If you are working on a migration project from SQL Server to Oracle, you will love this because it will save you refactoring all your client code that relies on this feature of T-SQL.
Mark said...Agreed.... Thanks for the reply.
Mark said...Hi Tim,
A little controversial perhaps but I suspect a lot of people won't be using this feature. There seems to be a new design paradigm where the middle-tier is responsible for business logic to promote database independence. Any ideas where this comes from? Do you have any opinions on the subject?
If you speak to a .NET or Java person, they will say middle tier. If you speak to a database person, they will say database. They all have their +/- points. :)
The answer is database. :)
Mark said...Good call Sir!
We just need to convince the thousands of middle tier developers.
Tim... said...That is going to take some doing. :)
I am using linked servers from sqlserver to oracle and i needed something like this like crazy. This will be very helpful when dealing with vertical and horizontal filtering a dynamic generated sql.
Too bad this is available only in 12.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!