Stored procedure call escape ({call ...}) support

[Lance Andersen - Oracle]

What you are outlining is really more of a function vs a Stored Procedure call.

The escape syntax for call is geared around Store Procedures though for many backends it will work with functions.

In your example,  I would not think would work with many databases

Best

Lance
On Jan 17, 2013, at 10:47 AM, Mark Rotteveel wrote:

> On 3-1-2013 17:02, Lance Andersen - Oracle wrote:
>> yes as  Escape syntax is supposed to be generic not implementation specific
> 
> Another question regarding the escape syntax, should the call escape be the entire statement, or can (must?) it also be supported as part of another query (say: SELECT * FROM some_table WHERE column1 = {call storedproc_with_returnvalue(?,?,?)})
> 
> Mark
> -- 
> Mark Rotteveel

-------------- next part --------------

Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering 
1 Network Drive 
Burlington, MA 01803
Lance.Andersen at oracle.com