Re: Naming conventions for special database objects

"--CELKO--" <jcelko212@[EMAIL PROTECTED]
> wrote in message 
news:18cd6fae-b8d5-4fee-adc6-2f237fad9a6a@[EMAIL PROTECTED]
>>> I am currently doing a review of my personal database naming
conventions 
>>> and found that there are not much (good) examples in the
> literature for some special objects. <<
>
> Have you looked at the ISO-11179 Standards?  I happen to have a book
> on this topic, SQL PROGRAMMING STYLE, based on the Standards and few
> decades of research in code readability.
>

(SNIP)

>>> 5) Primary key constraints, Foreign key constraints ..<<
> I tend not to put a constraint on them at all.  Their nature does not
> change much so I don't need to reference them.

Obviously you meant "I tend not to put a constraint name on them at all." 
(My personal preference as well.)

 >If there is an error,
> then the message includes that they are PK or FK, so the constraint
> name adds no information.
>

Aren't you assuming that all DBMS vendors will provide adequate PK/FK info

(without the constraint name) when an error occurs?  There could be
multiple 
FK columns on a table which reference the same PK table (e.g., a PK  table

of valid states or countries).