(sorry if this is a duplicate)

Hi Martijn,
I wondered whether this whole issue is something belonging to Firebird
itself or if tools/connection components would be an equally appropriate
place to provide something similar.

Firebird transforms field names (regular identifiers) to UPPERCASE, but
why should DB Workbench and other tools do the same? I mean, I'm happy
with Firebird creating the table PERSON with the fields FIRSTNAME and
LASTNAME when I write something like:

create table Person(ID Integer, FirstName Char(20), LastName Char(20));

but I don't see why that should prevent DB Workbench from returning

id FirstName LastName
1 Martijn Tonies
2 Svein Erling Tysvaer

(as opposed to
ID FIRSTNAME LASTNAME)

when I issue

select id, FirstName, LastName
from person

(i.e. use the case from the request rather than field names returned
from Firebird)

My question is, do all tools - and if so why do all of them - uppercase
the resulting column name just because Firebird does so in the table? Is
there something preventing you from using the case that the user wrote
when issuing the SELECT?

Though don't consider this as a feature request, I'm happy with DB
Workbench as is (though I'll soon have to upgrade, so that I can check
if the niggles I encounter with my old version are still an issue with
the 3.0 version).

Set

Martijn Tonies wrote:

> If the difference between case sensitive and case preserving is
> stored in the metadata tables, those tools "just" need to support
> this new feature.
>
> For example, in Database Workbench I'm checking to see if
> it's not all uppercase, if so -> quoted. If it has special characters
> -> quoted, and so on.
>
> If it's a simple name, all uppercase -> not quoted. Quite easy
> actually.
>
> Martijn Tonies