#4002 introduced the unenforced primary key concept, but the key is unordered because we just record a primary key boolean at the field level. @majin1102 brought up this in #4207 (comment).
I thought about this a bit, it's probably better to make it ordered for future potential use cases. For example, we could build a multi-column b-tree index for primary key columns instead one one for each column, and in that case the order of the column would affect the effectiveness of the b-tree.
#4002 introduced the unenforced primary key concept, but the key is unordered because we just record a primary key boolean at the field level. @majin1102 brought up this in #4207 (comment).
I thought about this a bit, it's probably better to make it ordered for future potential use cases. For example, we could build a multi-column b-tree index for primary key columns instead one one for each column, and in that case the order of the column would affect the effectiveness of the b-tree.