Re: Optimizer hints in PL/SQL's embedded SQL

Hi, Visctor
Thanks for assistance.

The proper way is
1) to separate hint and plus sign with a space 2) do NOT separate comment signs (-- or /*) and plus I. e. following egs. are correct:

SELECT /*+ INDEX(E) */ ....
or
SELECT --+ INDEX(E)
...

Regards
  Sergey Balter
"VSE" <vsmeu_at_yahoo.fr> сообщил/сообщила в новостях следующее: news:aplll7$3m5$1_at_reader1.imaginet.fr...
> Hi :)
>
> I 'm not sure but I think that "hints" syntaxe is ( your example ) :
>
> SELECT /* +INDEX(E) */ E.Id INTO AId FROM DocSpec E, .....
>
> Is not :
> SELECT /*+INDEX(E)*/ E.Id INTO AId FROM DocSpec E, .....
>
> So /* toto */ not /*toto*/
>
> Scuze me for my english :)
>
> Regards ;)
>
>
> Victor
>
>
>
> "Sergey Balter" <balter_at_kompas.donetsk.ua> a Иcrit dans le message news:
> aplh8f$16nl$1_at_dipt.donbass.net...
> > Hi, All,
> >
> > When I write something like
> >
> > procedure test is
> > AId Integer;
> > begin
> > SELECT /*+INDEX(E) */
> > E.Id INTO AId
> > FROM DocSpec E, .....
> > .........
> > end;
> >
> > SQL Engine absolutely ignores hint /*+INDEX(E)*/
> > Maybe PL/SQL quesses it's comments :-(((
> >
> > I am forced to bypass the problem using EXECUTE IMMEDIATE
> >
> > Is it the unique way? Does anybody know about specifying optimizer
> > hint in in PL/SQL's embedded SQL?
> >
> > Regards,
> > Sergey Balter
> >
> >
> >
>
>
Received on Fri Nov 01 2002 - 02:17:58 CST