> While lurking into the dev list of Firebird, I saw a suggestion that
> for 2.0, could be 'case preserving' for fields names, table names ...
>
> quote
> Case insensitive meaning that it doesn't matter how you
> type an object name: TBLCUSTOMERS = tblCustomers = tblcustomers =
> TbLCustOMerS but so that when you use soemthign like IBObjects or D7
> intellisense, the object comes up the way you created it. So if you
> created it as tblCustomers it always comes up tblCustomers unless you
> decide to change it manually.
>
> /quote
>
> and all this without the double quote business.
>
> In a case-sensitive language like PHP, do you see this as a benefit or
> a drawback ? Surely this would have an impact on quite a number of PHP
> scripts. I could be a good time to have a think about this.

Coming from a time when dBAse only handled upper case names,
I've tended to stick to that for all SQL names. Then they
stand out from the other variables which makes life easier.
So it does not cause me any problems.

What does is the 'reserved words' which get used in MySQL
applications, and stop me from porting some of the nice
stuff over. Even when the package uses ADOdb and quite
happily works except for needing the quotes, or a change of
name in the application!

Aren't standards great :)

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services