Age | Commit message (Collapse) | Author |
|
|
|
|
|
Use a new `yaqlite::Error` type. Remove the other error types and use
this main error type everywhere. For now, that seems simpler.
The real reason why I centralised on one error type is that I wanted a
single `Error::Sqlite` variant for both `rusqlite::Error` and
`SqliteError` errors. However, I wasn't sure if it's possible to do that
with `thiserror`, and I didn't want to bother having to write my own
`std::error::Error` impls.
|
|
|
|
|
|
If any value extraction comes back as `None`, convert it to a SQL
`Null`.
|
|
Return a `Result` and wrap errors in a `thiserror` struct.
|
|
That is now moved to `yaqlite::insert()`.
|
|
Found some documentation that reminded me how unit structs are written.
Change this definition as that makes more sense.
|
|
|
|
|
|
Test that a plain YAML hash gets inserted even when not wrapped in an
array.
|
|
Check that nonexistent columns are ignored from the input YAML.
|
|
|
|
Extract the test code to a new function so that it can be reused to test
other YAML inputs and database records.
|
|
Check that the function inserts a record into the database based on a
YAML input.
Adjust the `extract()` function to take the table name as an argument.
|
|
Make an interface that more cleanly says "insert this YAML into this
database".
|
|
|
|
Want to use `yaqlite::yaml` for the YAML extraction function.
|
|
Remove the hard-coded table name.
|
|
|
|
|
|
|
|
Turns out I didn't need the type of the column, so get rid of that value
and resume using `Zero`.
|
|
Separate this code from the main binary file.
|
|
If a hash key in the input YAML does not match one of the column names
in the table we're inserting into, ignore that YAML field and use the
other columns for insertion.
|
|
This enables us to build a list of params for insertion and insert them
into the database.
Not sure if `NULL` makes sense for all of these types, but this at least
gives us the type conversion necessary to get the YAML values into the
SQL query, cool.
|
|
Doesn't work yet as I need a way to convert `Yaml` values to Rusqlite
SQL params.
|
|
Need to figure out what to do for NUMERIC affinity since Rusqlite
doesn't expose a variant for that pseudo-type.
|
|
|
|
|
|
Creates a map from column name to type.
|
|
|
|
Want to translate YAML types to SQLite types.
|
|
Need to figure out how to insert `table_columns.len()` values.
|
|
Possibly ugly passing `table_columns` into `yaml_extract`, but just
trying to get things working for now.
Query a "people" DB table instead as that matches the test YAML file.
|
|
Make it easier to find out if a column name exists in the table.
|
|
We probably don't even need a transaction for a `SELECT`. Get rid of
that code and remove the `mut` on `dbconn` which was only necessary for
the transaction.
|
|
Eliminated the transaction because of a borrow problem.
|
|
|
|
|
|
$ rustc --version
rustc 1.59.0 (9d1b2106e 2022-02-23)
$ cargo init --bin
|