Subject | Re: Field names upper case - true of firebird 2.0 also? |
---|---|
Author | MichaelS |
Post date | 2005-05-09T12:34:44Z |
--- In firebird-support@yahoogroups.com, "Martijn Tonies"
<m.tonies@u...> wrote:
issues that case flexibility brings to firebird. Just this AM it sunk
in, that the flexibility firebird allows effectively forces one to
jump through extra hoops in order to keep it all working, and that it
wouldn't be worth it (Helen hinted at that).
Well, this is the first thing about firebird that I really don't like.
Shoot. Doesn't seem like it's going to change anytime soon either.
<m.tonies@u...> wrote:
> Hello Michael,...
>MS SQL
> If you want to create a delimited identifier (one in which you case
> use mixed case), you have turn it ON in the database registration
> options.
>
> However, if you create your table like "tlkpCountry" - you will have
> to use double quotes _everywhere_ ... eg:
>
> select * from "tlkpCountry"
>
> This will fail:
>
> select * from tlkpCountry
>
> and this as well:
> select * from TLkpCountRY
>
> Once used with non-uppercase and double quotes, you will have
> to use quotes always.
>
> Most people find this very very very annoying, that is why Database
> Workbench uppercases the names for you unless you explicitly turn
> it OFF.
>
> With regards,
>
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL &
> ServerThanks, Thomas helped with the tool aspect and Helen laid out the
> Upscene Productions
> http://www.upscene.com
issues that case flexibility brings to firebird. Just this AM it sunk
in, that the flexibility firebird allows effectively forces one to
jump through extra hoops in order to keep it all working, and that it
wouldn't be worth it (Helen hinted at that).
Well, this is the first thing about firebird that I really don't like.
Shoot. Doesn't seem like it's going to change anytime soon either.