Re: Unsupported Feature?

Hi there, that makes sense except that I have NO CLOB's anywhere in the database....

Any other ideas? I am pretty new to Oracle so I am learning new things with it everyday.

I suspect it is the way that the Component One control is wording it's returning SQL statement but I don't have any control over it and can't even see what it is...

Regards,
Dean

"Jusung Yang" <JusungYang_at_yahoo.com> wrote in message news:130ba93a.0301161104.6e16c1de_at_posting.google.com...
> Does your table have a CLOB column which your trigger tries to insert
> data into? If yes, you probably hit the ORACLE bug (not a bug,
> according to ORALCE, even though it has a bug number assigned)
> #1992006.
>
> When CLOB is invloved, ODBC driver actually changes your insert
> statement and try to return the "clob locator" with a "returning"
> cluase to the client. Since the statement is changed again by the
> trigger, ORALCE does not know what to return, hence the error. From
> SQL*PLUS, you use plain insert without the returning clause, so there
> is no error.
>
> Before going any further, let's make sure that CLOB is indeed the
> cause of problem in your case. You can also look up this bug for more
> details.
>
>
> - Jusung Yang
>
>
>
> "Dean Harry" <dean_at_ganda.net.au> wrote in message
 news:<clwV9.18855$UB4.81804_at_news-server.bigpond.net.au>...
> > Hi World,
> >
> > I am using Oracle 8i with Visual Basic 6 and Component One's True Data
> > Control.
> >
> > I am trying to add a row to a view and keep getting the error
 'unsupported
> > feature with RETURNING clause'.
> >
> > I have an INSTEAD OF trigger on on the view which appears to be working.
> >
> > I can add rows to the view using SQL+ with no problems.
> >
> > UPDATE's and DELETE's for fine it's only when trying to INSERT a new row
> > that this occurs.
> >
> > Component one tell me that it is an Oracle issue but I can't see it.
> >
> > Any Ideas would be great.
> >
> > Regards,
> > Dean Harry
Received on Fri Jan 17 2003 - 00:24:57 CET