rorm
rorm copied to clipboard
A multi-language ORM written in pure rust.
This is an direct limitation from the orphan rule. But as a result other crates are greatly limited in adding new `FieldType` because the can't work with `Option`.
Only `FieldEq` are implemented for `ForeignModelByField`. It would be more intuitive, if we could forward all `FieldEq` impls from `FF::Type` to `ForeignModelByField`.
When generating the unit struct for a field, `rorm` uses the type specified in its model to populate the `Field::Type` associated type: ```rust struct SomeModel { id: Id, } impl...
`impl for Option` should read `impl for Option` and likewise for the borrowed version
```rust query!(&db, Foo) .condition(DynamicCollection::or(vec![])) .all() .await?; ``` As it may happen that we provide no entries in a dynamic collection, I'd vote for some pattern to check before providing the...
Can we provide a way for the user to explicitly set the way the model creation works? I think of different high level settings: - Include all Models that are...
Is there any way to check if all necessary fields (not null, without default, without auto_create_time, id) are in patches that are used in `insert!` statements? Happened recently to me,...
`commit` will put up the wrong expaction for the user that the transaction will commit, what's not necessarily the case, if the transaction is not owned
The `and!` and `or!` macro produce a somewhat intimidating error message, when one of its arguments don't impl `Condition`. For easier troubleshooting the message should just point to the violating...