At 03:46 AM 9/05/2005 +0000, you wrote:

>I'm quite unused to firebird's apparent use of uppercase letters for
>field names etc. Is this an acutal requirement, or is it optional?
>What about firebird 2? If it's a requirement, why...don't like it any
>more than I would if I was forced to type this msg in uppercase.
>Varying case helps so much with names:
>
>tblItem
>tblItem.ItemID
>tblItem.ItemName
>
>Much nicer than
>
>TBL_ITEM
>TBL_ITEM.ITEMID
>TBL_ITEM.ITEMNAME
>
>Feels like using dBase...
>
>I have the firebird book

See Chapter 14, pp. 218-9, "Database Object Naming Conventions and
Constraints". Firebird's convention is in conformance with the Standards,
so no change is forthcoming in Firebird 2.0 to make C programmers feel more
cosy.

>(as an ebook, what a mistake!)

Agreed. As the civilised world defines an eBook, it aint no eBook. It's a
compositor's proof. :-( Feel free to read my comments about it at the
IBPhoenix website. There are one or two tips there that might help to ease
the pain.

btw, I too prefer the Pascal camel case naming conventions and use them in
my DDL. As long as you avoid double-quoting your object identifiers, the
Fb engine happily accepts any combination of case on identifiers, both when
declaring and altering objects and when referring to them in queries.



./heLen