Subject | Re: [Firebird-Architect] Multi-level name space |
---|---|
Author | Lester Caine |
Post date | 2006-01-13T08:08:59Z |
Claudio Valderrama C. wrote:
'problem' I see is that hungry."wolf" becomes HUNGRY.wolf in Firebird
but hungry.wolf elsewhere. Just something to keep an eye on as far as I
am concerned, but I already have to watch it in all the PHP stuff!
My only question is "Is VARCHAR(256) enough, would VARCHAR(512) cause
any problems?" Then one can have large UNICODE names as well and we do
not have to worry about another increase later?
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.
>>-----Original Message-----And so they must to be compatible with other databases. The only
>>From: Firebird-Architect@yahoogroups.com
>>[mailto:Firebird-Architect@yahoogroups.com]On Behalf Of Jim Starkey
>>
>>Almost nothing changes except the max length of table names and the name
>>matching rules in the BLR and SQL compilers.
>>
>>It seems too simple. What am I missing?
>
>
> Quoted identifiers.
>
> "hungry.wolf" and "hungry"."wolf" will become undistinguishable.
'problem' I see is that hungry."wolf" becomes HUNGRY.wolf in Firebird
but hungry.wolf elsewhere. Just something to keep an eye on as far as I
am concerned, but I already have to watch it in all the PHP stuff!
My only question is "Is VARCHAR(256) enough, would VARCHAR(512) cause
any problems?" Then one can have large UNICODE names as well and we do
not have to worry about another increase later?
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.