DDC-301: Column in Table used as PrimaryKey should be set to notnull = true #373

Closed
opened 2026-01-22 12:36:19 +01:00 by admin · 1 comment
Owner

Originally created by @doctrinebot on GitHub (Feb 4, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user @beberlei:

A column which is created with 'notnull' => false and then added to a primary key is not a valid state of a schema.

Setting columns as primary keys should explicitly alter their not-null status to true.

Originally created by @doctrinebot on GitHub (Feb 4, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user @beberlei: A column which is created with 'notnull' => false and then added to a primary key is not a valid state of a schema. Setting columns as primary keys should explicitly alter their not-null status to true.
admin added the Bug label 2026-01-22 12:36:19 +01:00
admin closed this issue 2026-01-22 12:36:19 +01:00
Author
Owner

@doctrinebot commented on GitHub (Feb 4, 2010):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Feb 4, 2010): Issue was closed with resolution "Fixed"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#373