>
>> Is is worth adding yet another setting, eg. set sql92=strict, which would
>> disallow such flagrant breaches of the standard? Maybe it could even be set
>> as the default in template1? I understand that breaking legacy code is a
>> bad idea, so the warning is a good step, but I would prefer an error if I
>> ever write such a statement.
>
>I am concerned about overloading the SET command. Seems we should just
>agree on a behavior.
>
Then make it an option at build time.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: +61-03-5367 7422 | _________ \
Fax: +61-03-5367 7430 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
