[EMAIL PROTECTED] writes:
> If you have a primary key on several columns, each of these columns is
> given the 'not null' modifier. I can't see why this is required.
(A) it makes no sense otherwise, and (B) the SQL spec says so:
A unique constraint is satisfied if and only if no two row
Laurent Martelli ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
multicolumn PRIMARY KEY introduces wrong 'not null' fields
Long Description
If you have a primary key on several columns, each of these columns is given the 'not
