Re: Oracle functions and where clauses
Date: Mon, 17 Mar 2003 15:23:56 -0500
Message-ID: <ebqda.24390$eD6.226085_at_wagner.videotron.net>
I have used that syntax before to call functions and it works well. The only problem is the "where clause" it does not seem to be possible to do that with a function. It is possible in a MSSQL and Interbase though.
Thanks for answering,
José.
"Gabriel Gonzalez" <no-spam_at_no-spam.com> wrote in message
news:e7qdnR9VZ6Jli-ujXTWchA_at_giganews.com...
> Well, remove the OLEDB provider from the equation: Try it in SQL plus
> first. How you are calling the function presently makes no sense because
> Oracle cannot make a call to the OLEDB on your client machine (which is
what
> it would have to do in order to evaluate the function call presented in
> OLEDB syntax)
>
> "José Ramón Rodríguez" <jrrodriguez_at_multicorpora.ca> wrote in message
> news:kzoda.14592$8q2.181056_at_weber.videotron.net...
> > Thanks for answering,
> >
> > I am doing it like that because it seems I am forced to use that syntax.
> > That's the syntax the OLEDB provider for Oracle documentation uses all
the
> > time to call functions. I have tried it before with the syntax you
suggest
> > (which makes a lot more sense to me) and it gives an error too, it does
not
> > seem to recognize that syntax well.
> >
> > José.
> >
> > "Gabriel Gonzalez" <no-spam_at_no-spam.com> wrote in message
> > news:CTOdnUhR5vhDneujXTWcjA_at_giganews.com...
> > > Why are you doing this? Try this:
> > >
> > > select * from MC.SEC.QryTermbases(?, ?) where ID = ?
> > >
> > >
> > >
> >
> >
>
>
Received on Mon Mar 17 2003 - 21:23:56 CET