#2 Use per-entity ID type

Closed
opened 2 years ago by kestrel · 0 comments
kestrel commented 2 years ago

Rather than the current universal query::ID rowid wrapper, ideally we want an entirely separate type so that the compiler can help with accidental cross-table ID use.

The problem with this is mostly the column names of serialized structs (especially newtype structs) are not currently clear, and if there are multiple (e.g. for a struct S (i64, i64)) then it's not clear to the derive macro exactly how many table columns there are.

This may mean that we are limited to newtype structs and tuples, as tuples should be handlable with a .i suffix.

Rather than the current universal `query::ID` rowid wrapper, ideally we want an entirely separate type so that the compiler can help with accidental cross-table ID use. The problem with this is mostly the column names of serialized structs (especially newtype structs) are not currently clear, and if there are multiple (e.g. for a `struct S (i64, i64)`) then it's not clear to the derive macro exactly how many table columns there are. This may mean that we are limited to newtype structs and tuples, as tuples should be handlable with a `.i` suffix.
Sign in to join this conversation.
No Label
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.