[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ProgSoc] NULL values in primary keys in MySQL
I understand it's bad design, and I get that what I probably want
is a unique key rather than a primary one, and I get that I should
read up (again) on normalisation, and I'm well aware that NULL
!= NULL ... but all that aside (and AFAIK that all *is* an aside)
what's the logical, or even technical reason for why you can't have
a primary key that contains columns that may contain a NULL entry?
Jedd.
-
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to progsoc-request@xxxxxxxxxxxxxxxxxxx
If you are having trouble, ask owner-progsoc@xxxxxxxxxxxxxxxxxx for help.