|Subject||Re: [firebird-support] exists(EXECUTE STATEMENT ...|
> HB> 5. For me (as a Pascal programmer) they break the standard Pascalcoding
> HB> conventions which I, along with most Pascal coders, follow. Javacoding
> HB> conventions are similar to Pascal's. I HATE having to handle codewritten
> HB> by people whose only justification for using these infernal quotes isto
> HB> enable case-sensitive identifiers. Non-C programmers get alongadmirably
> HB> despite lacking the ability to code hidden traps like two variablesnamed
> HB> first_name and FIRST_NAME.Yeah... that's a good reason ;-)
> 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.
> 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 increasesTrue.
> readability a lot (I'm using IBExperts "Generate HTML
> documentation" feature)
> 4. I can avoid the separator "_" as I use "FirstName" not FIRST_NAME. OnAnyway, you can still write
> longer identifiers as "PersonsFirstName" or PERSONS_FIRST_NAME
> there is no difference in length any more.
SELECT FirstName, Adress, LastName
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 :-)
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL