Re: integer id columns for all tables

JOG wrote:

Alexandr Savinov wrote:

garhone schrieb:

- If you need uniqueness then use the corresponding constraint.
Frequently the need for uniqueness in a property leads to the conclusion
that it should be used as an identifier.

Not if one realises that uniqueness is not the only quality a good
identifier has. See bob's informative list in his post.

Even better--go to where Bob got his informative list:

http://www.dbdebunk.com/page/page/622344.htm
.

Relevant Pages

  • Re: Creating duplicate rows of data based on a determined number o
    ... As each record goes through it's production life, ... they will begin to gain uniqueness. ... id and other common info will be its identifier. ... "Jeff Boyce" wrote: ...
    (microsoft.public.access.externaldata)
  • Re: satisfies algorithm
    ... systems built with commercial implementations that pervade the industry, ... where there is a unique constraint or a primary key constraint that needs ... Of course you can validate uniqueness without an index: ... Enforcing the uniqueness property of a ...
    (comp.databases.theory)
  • Re: satisfies algorithm
    ... systems built with commercial implementations that pervade the industry, ... where there is a unique constraint or a primary key constraint that needs ... trigger or an assertion to enforce uniqueness. ... is a wealth of material on optimisation. ...
    (comp.databases.theory)
  • Re: uniqueness of {if,do,case}-construct-name
    ... Is such a constraint mandated by the standard? ... Section 14.2 is concerned with labels, and the BNF of DO in ... do-construct-name is not a label. ... requires the uniqueness of the name within a scoping unit. ...
    (comp.lang.fortran)
  • Re: Do I need a PK on a join table?
    ... uniqueness) with a physical structure. ... Uniqueness is a logical constraint. ...
    (comp.databases.theory)