Primary Keys and Properties

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

If you set a field to be a primary key why do the properites for that field
not change accordingly. For instance, the Allow Zero Length property remains
as it's default of "YES" which is a contradiction of a primary key property.
And the Required property remains as the default of "NO" again a
contradiction of the concept of a primary key. The Index proeprty is updated
properly to reflect a primary key why aren't the other properties updated?
 
It is unnecessary to both set the index properties and also set the field
properties.

By definition, a primary key is not nullable, so setting the Required
property of the field as well is as superfluous as pulling switching the
computer off as well as pulling out the power plug.
 
Why do you say that Allow Zero Length of Yes is a contradiction of the
primary key property? That would be true if the field could contain Null,
but a zero length string isn't the same as Null. If you didn't allow Zero
Length and you didn't allow Null, what would you put for people who don't
have a middle name (for example)?
 
Back
Top