Re: [cx-oracle-users] an old question

[Glyph <gl...@tw...>]

On Apr 30, 2013, at 1:04 AM, Mark Harrison <mh...@pi...> wrote:

> On 4/30/13 12:21 AM, Glyph wrote:
>> As I keep pointing out:
>> 
>>>> Currently, I'm doing this with host variables, but that's a limited solution [...]
> 
> You're trying but apparent failing to make your point...
> 
> I tried helping you out earlier, but your response left me not
> caring a lot whether or not you solved your problem or not.

I do appreciate you taking the time to help, even if your answer wasn't directly useful to me.  I realize what I'm looking for is a bit esoteric.  "What you are trying to do is impossible" is a totally acceptable answer - I am really just trying to understand why Oracle makes this impossible. 

The database-specificity of cursor.var() makes sense to me, idiomatically, but the restricted size of query results seems odd.  For example, if I want to 'delete...returning...into...' a million rows, rather than the default allowed ~1000 or so, how can I do that?  Would a pipelined procedure with PIPE ROW address this problem, and the general expectation is just that I'd be able to put such a procedure into my schema?

-glyph