meuter / miniorm-rs Goto Github PK

Implementing a REST axum router (#9) directly on top of Store is probably not a good idea. What if someone wants to use the use the Router on some other data structure that provides CRUD operations. One should be able to to that.

Rust's answer to that is to define a Crud trait that contains all of the necessary functions and build a router on any type that implements this trait.

SELECT COUNT(*) FROM {table}

Multiple issues to figure out to integrate the MySql backend:

1. The placeholders syntax is different ? (supported by MySql and Sqlite) vs $i (supported by Sqlite and Postgres)
2. MySql does not support RETURNING id in the create and update query. Sqlx has last_insert_id() method on MySqlQueryResult, unclear if this works for UPDATE queries. But that means that we need to use a Query, not a QueryAs so the Bind trait is notsuitable as is because it only allows to bind against QueryAs

Given a Store that implements all the necessary CRUD operations, one should be able to create an axum::Router that handles all of these operations over a REST API, provided of course the the entity type implemented serde::Serialize and serde::Deserialize.

• GET / will list all entities,
• POST / will create a new entity,
• PUT / will update an existing entity,
• DELETE / will delete all entities
• GET /:id to retrieve one entity from the store
• PUT /:id to update one entity in the store
• PATCH /:id to update one entity in the store - PATH or PUT or both?
• DELETE /:id to delete one entity from the store

The main issue here is that on top of having to serialize/deserialize the entities, we also need a way to pack the id returned by the database. Introducing a wrapper type WithId<E,I> { inner: E, id: I } might be a good option here.

• The documentation of miniorm_macros is lacking
• Feature flags are not properly documented
• and more...

https://docs.rs/sqlx/latest/sqlx/trait.FromRow.html