> >Is Firebird 1.5 supposed to distinguish between upper and lower
> >cases?
> >For instance, can we have a table named "ACCOUNT" and another one
> >named "account" in the same DB?
>
> Yes.
>
> >If the answer is YES, is it possible to tell Firebird NOT to do it?
> >("my" Firebird is doing it, I can have tables named that way, and
> >it's bringing me problems in using it)
>
> "Your" Firebird is doing it because you are using some third-party tool to
> create your tables and it is imposing double-quoted identifiers on you.

If

> you don't use quoted identifiers in your DDL, it doesn't matter what case
> you use in the definition statements, Firebird will store them all in

upper

> case and you can address them case-insensitively. Anything you define

with

> quoted identifiers will be case-sensitive and will have to be addressed
> always with those danged quotes.
>
> Find a setting in the tool to stop this; or use a different tool that

does

> not force this absurd practice, which I think made its way into the SQL
> standard by way of Microsoft, who wanted Access fieldnames like "Walking
> Like a Gorilla" to be portable.

Naah, then it would have been [Walking Like a Gorilla] ... :-)

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com