Subject | Re: [firebird-support] Use of double quoted names in Firebird |
---|---|
Author | Lester Caine |
Post date | 2005-03-23T09:48:33Z |
Kjell Rilbe wrote:
be that some third party tools tend to add the quotes when they are not
actually needed, and I'm not sure it is still the case, but I do
remember hitting tools that did not accept quoted identifiers. I know
that some Eclipse plug-ins had a problem with that.
The move to tidy up 'internationalisation' and hopefully increase the
maximum length will help a lot. SQL Standard is up to 64 characters and
allows UTF-8 coding - so while we comply, increasing the length will
remove the need for my renaming fields converted from other engines ;)
(And an increase on the index length will help there as well :) )
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
> 2. Quoted identifiers should be (and are already) case sensitive andI'm not aware of any problems IN FB in this area. The PROBLEM seems to
> support national characters. What's new is here that all bugs in this
> area should be removed, in FB itself and in client tools etc. This would
> not break backwards compatibility - it would simply make life easier for
> those of us who want to use this new feature to its full extent.
be that some third party tools tend to add the quotes when they are not
actually needed, and I'm not sure it is still the case, but I do
remember hitting tools that did not accept quoted identifiers. I know
that some Eclipse plug-ins had a problem with that.
The move to tidy up 'internationalisation' and hopefully increase the
maximum length will help a lot. SQL Standard is up to 64 characters and
allows UTF-8 coding - so while we comply, increasing the length will
remove the need for my renaming fields converted from other engines ;)
(And an increase on the index length will help there as well :) )
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services