> HB> 5. For me (as a Pascal programmer) they break the standard Pascal

coding

> HB> conventions which I, along with most Pascal coders, follow. Java

coding

> HB> conventions are similar to Pascal's. I HATE having to handle code

written

> HB> by people whose only justification for using these infernal quotes is

to

> HB> enable case-sensitive identifiers. Non-C programmers get along

admirably

> HB> despite lacking the ability to code hidden traps like two variables

named

> HB> first_name and FIRST_NAME.
>
> HB> Now, you tell me what's *good* about them.
>
> Tat's not easy!
>
> 1. It's possible. Why? In Dialect 1 I didn't have a choice! In dialect
> 3 I do have.

Yeah... that's a good reason ;-)

> 2. I can use keywords as field names.

Which, IMO, is always a "not so smart" thing to do.

> 3. Mixed Case writing is visible in db documentation which increases
> readability a lot (I'm using IBExperts "Generate HTML
> documentation" feature)

True.

> 4. I can avoid the separator "_" as I use "FirstName" not FIRST_NAME. On
> longer identifiers as "PersonsFirstName" or PERSONS_FIRST_NAME
> there is no difference in length any more.

Anyway, you can still write

SELECT FirstName, Adress, LastName
etc...

if you have created the column as FIRSTNAME. :-)

IMO, the double quotes are a pain... And they were a pain
to implement properly in tools as well :-)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com