Express connection between SQL tables and columns in the Rust type system #218
Labels
No labels
A-build
A-cli
A-core
A-design
A-edn
A-ffi
A-query
A-sdk
A-sdk-android
A-sdk-ios
A-sync
A-transact
A-views
A-vocab
P-Android
P-desktop
P-iOS
bug
correctness
dependencies
dev-ergonomics
discussion
documentation
duplicate
enhancement
enquiry
good first bug
good first issue
help wanted
hygiene
in progress
invalid
question
ready
size
speed
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: greg/mentat#218
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In #640, I observed an infelicity in the way that we strongly type SQL tables (
DatomsTable
) and associated SQL columns (special types likeDatomsColumn
). When we addFROM
sources, column bindings, and column constraints, we generally don't have a strong type constraint on the table and associated columns. This ticket tracks making the Rust type system help us avoid errors. I haven't thought through this yet, but my first notion is to represent a table by a trait with an associated type representing specific columns.