> >> Tat's not easy!
> >>
> >> 1. It's possible. Why? In Dialect 1 I didn't have a choice! In dialect
> >> 3 I do have.
>
> MT> Yeah... that's a good reason ;-)
>
> Well, why did they implement it in dialect 3? :-)

To conform to the SQL standard and as a workaround
for reserved words.

> >> 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.
>
> MT> Anyway, you can still write
>
> MT> SELECT FirstName, Adress, LastName
> MT> etc...
>
> MT> if you have created the column as FIRSTNAME. :-)
>
> Yes, but I don't write it. I export the field list from tools via

clipboard!

:-)

> MT> IMO, the double quotes are a pain... And they were a pain
> MT> to implement properly in tools as well :-)
>
> Well, I don't want to implement a tool and I think my dbworkbench
> works perfectly with mixed case :-)

Yes, it does... :-D

With regards,

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