On 19 Oct 2001, at 16:52, Fabricio Araujo wrote:

> On Fri, 19 Oct 2001 11:48:57 -0500, Woody wrote:
>
> >Myself, I have no preference and could live with either one.
> >Personally, I don't think spaces should be allowed in table and field
> >names but other characters would be good such as hash marks, etc. to
> >denote special fields. Since I left C a long time ago, case sensitive
> >names don't appeal to me anymore so I think that quotes around a
> >field name should only signify the name may have special characters,
> >not that I want case sensitivity. Maybe I'm alone in that, but I've
> >been there before too. :)
>
> Since this is a M$-only thing, we don't need to support this on
> Firebird or Interbase. Let's follow the SQL way and ride the road.
>

I agree, for several reasons:

1) We still have official SQL standards to implement from SQL-99

2) We have better things to do, like implementing server side
aliases, and replacing the services API with something that makes
sense, and hopefully can be done with SQL.

3) Microsoft has a habit of changing the "standards" they define,
just ask a VB6 programmer what they think of VB.Net!

Paul


Paul Schmidt
Tricat Technologies
paul@...
www.tricattechnologies.com