On 8/8/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote:
Aye, Kevin be right...
But the next logical question is "why would you have a
table with no pkey defined at all?" Granted, it'll work,
but it's not ideal... maybe I'm just limited in my
understanding of things. ;)
As usual, everything depends on what you want to do with your table.
E.g. if your just logging certain events in your application, why
would you need a PK, and if so how would you define it? Or: what if
you don't want/need rows in your table to be updatable, for auditing
reasons?
Having found out the hard way, I agree that PK are mostly a good idea
- but a good relational database design does not require them on ALL
your tables.
Wouter
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
