Hi,

> > I would rather say there's nothing wrong at all with compound
> primary keys,
> > but that using a column with a MEANING (like artikle codes, part
> numbers
>
> What about timestamps? Such column has meaning, but I do not see any
> reason, why not to use it in compound PK. Or am I wrong?

Not really, except that updating a row involves listing the value:

UPDATE ... WHERE mypkcol1 = 10 and mypktimestampcol = '12/04/2002 12:40:51'

which seems akward to me ...



With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."