-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(structured data) core
endpoints to CRU rows
#2478
Conversation
d824f31
to
9af8435
Compare
9af8435
to
d8e455b
Compare
listing database rows
d8e455b
to
91ea7ea
Compare
core
endpoints to CRU rows
get(databases_rows_retrieve), | ||
) | ||
.route( | ||
"/projects/:project_id/data_sources/:data_source_id/databases/:database_id/rows", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be tables/table_id ?
struct DatabasesRowsListQuery { | ||
offset: usize, | ||
limit: usize, | ||
table_id: Option<String>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a bad design to fetch all at once. We never want to do something with 2 rows from different tables and can always parallelize
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We never want to do something with 2 rows
We kind of do when we generate the schema from scratch though, no ?
as per slack, merging and addressing comment in #2489 |
list, get and upsert DB rows
remaining code to complete #2210