At 14:14 31/10/00 +0100, Zeugswetter Andreas SB wrote:
>>
>> Which is why I like the client being able to ask the
>> optimizer for certain kinds of solutions *explicitly*.
>
>Yes, something like:
> set optimization to [first_rows|all_rows]
>
That's one way that is usefull for affecting all subsequent statements, but
it would be nice to also allow such things in each statement, eg. in comments:
/*++optimizer: fast_start, no_seq_scan */ select...
ie. make all settable values dynamically settable in a statement. The scope
of the settings would probably have to depend on the abilities of the
optimizer - eg. how would subselects and views be handled?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/