Declaration of Leszynski Reddick Naming Convention

J

John Smith

I, John Smith, do hereby declare that:

1. Entity Relational Modelling in Visio requires strong naming conventions.
2. Leszynski Reddick Naming is a fantastic convention and very extensible.

All data models in the world must comply with Leszynski Reddick or else they
are not valid.

Well-formed UML Data Object diagrams will also comply or be deemed invalid
by me.

John Smith
God of Naming Conventions
 
C

--CELKO--

I assume that you have never heard of the ISO-11179 standards. And I
have you beat out for the "god" position. I have a book on SQL
PROGRAMMING STYLE coming out in a few months which has a few chapters
on naming conventions based on ISO-11179 and reading studies.
 
J

John Smith

Very Interesting, notably
http://jtc1sc32.org/doc/N1051-1100/32N1073T-FCD11179-5.pdf

If you are writing the book, then you DO have me beat as God.

Then, perhaps I can appeal to you to be the Son of God.

Well, actually 20,000 Sons and Daughters of God died of the effects of
poverty today (DIRECT BLOOD RELATIVES TO JESUS CHRIST).

And the Pope died last week (VERY DISTANT RELATION TO JESUS CHRIST).

Anyway, if you are writing a book, please do not suggest that all keys have
the suffix "ID".

It is utter blasphemy to suffix keys with ID!

And spare your readers "underscore HELL".

I_HATE_UNDER_SCORES. THEY_SUCK!

What a waste, and everytime you need one, you have to press the shift key,
unless you program your keyboard. Why in GOD'S NAME did IBM introduce the
UNDERSCORE?????

And CALL A KEY A KEY, not ID!

For example:

intClientPK, intEmployeePK, intEmployeeFK.

So intuitiive! And completely in league with ISO 11179 (notice_no_hyphen)

If all the tables in the world had no Underscores, developers live's would
be WAY EASIER!

John;
 
Top