#2 Use per-entity ID type

Kapalı
kestrel tarafından 2 yıl önce kere açıldı · 0 yorum
kestrel 2 yıl önce olarak yorumlandı

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.
Giriş yap bu konuşmaya katılmak için.
Etiket Yok
Kilometre Taşı Yok
Atanan Kişi Yok
1 Katılımcı
Yükleniyor...
İptal
Kaydet
Henüz bir içerik yok.