Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Define scope and capabilities #1
I think is good idea to define the scope of this crate. Also, to look at libraries/specifications like
Some traps I hope we avoid:
This is tied to the first point. Not asume I have a struct to put the data.
The base of this is very simple: Execute commands, return selects of many rows, return selects of scalars, alike micro-ORMs like https://github.com/StackExchange/Dapper
How is this a trap? Or even in the scope of this project? Ideally you want to be able to support both of such layers from Rust-DBC.
Granted SQL is relational. However - Relational Algebra is based upon Heterogenous Tuples† i.e. records. The mentioned tabular data is just a
†By Heterogenous Tuples I mean, when you execute following DDL:
To add my two cents to the discussion is below:
Sorry, was more like a observation than a trap.
Yes, I agree. I write this part poorly. I mean "just return a record as if is not a part of a set".
Normally I will be against this, but considering that crates make easy to mark something as optional, I think in rust is ok.
Tangential, maybe a way to declare "field types" so I can add after the fact a new kind of type. For example, imagine I need to turn a Json string inside some fields.
SQL interfaces look quite similar in other languages.
Does anyone have any preference as a starting point?