
> >Yes, I think syntax to force or disallow a particular index,
> >choose a join method or order, force/disallow seq scans ...
> >is sometimes useful.
> >Even Informix, who always refused to supply such a feature
> >now has it.
> 
> Can you give some sample syntax, for those of us who aren't
> really database people but merely trying to maintain a facade? :)

SELECT {+ INDEX (a auftragsbeleg_index2)} a.id_beleg
        FROM auftragsbeleg a, instparameter i WHERE 
        a.num_mandant=i.num_mandant AND cod_prioritaets=?
        AND num_prior_eingang<?
  
SELECT {+ ORDERED } * from tab1, tab2, tab3 .....

SELECT {+ FULL (tab1) } * from tab1, tab2, ....
SELECT {+ AVOID_FULL (tab1) } * from tab1, tab2, ....

Informix places the directives in comments, so that the resulting sql
does not violate SQL92.
The directive is identified by the {+

Andreas

Thu, 27 Jan 2000 10:55:10 +0100
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>
AW: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates 