Subject Re: [firebird-support] Re: Field names upper case - true of firebird 2.0 also?
Author Martijn Tonies
Hello Michael,

> > >It's certainly a well written book. Thanks for that and I hope there
> > >will be a revision for 2.0.
> >
> > There will be.
> >
> >
> > >I've read the section you pointed to and I don't see anything that
> > >seems to indicate that table names and field names must be uppercase,
> > >quite the contrary, they seem to be allowed (first line of quoted
> > >passage below).
> >
> > Correct. Any combination you like. But unquoted identifiers are
> always
> > *stored* in uppercase.
> >
> > >But, the tools I'm using seem to force upper case and
> > >I interpreted your msg as confirming my fear that uppercase was
> enforced?
> >
> > "Enforced" in the sense that you don't have the option to store
> > case-sensitive identifiers unless you enclose them in double-quotes.
> >
> > [..snip TFB quote..]
> > . In dialect 3, you can delimit "illegal" identifiers using pairs of
> > >double-quote
> > >symbols. Details follow.
> >
> > It's the details that follow that explain how you can force the
> engine to
> > store case-sensitive identifiers (and make a rod for your back in so
> doing).
> >
> > ./hb
>
> Hmm...still pretty confusing, for intance in DB Workbench, I've
> created a dialect 3 db, and can't find a way to build a table name
> like "tlkpCountry". The editor main table name field cares nothing for
> the double-quotes, all my entries are converted to upper case, and the
> two DDL screen dont' seem to be editable.

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 & MS SQL
Server
Upscene Productions
http://www.upscene.com