You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- (Improvement, **breaking**) The `record` macro no longer derives `Debug` and `Clone`, but now accepts custom attributes (such as derives and doc comments) similar to `sql_enum`.
3
+
- Added some additional doc examples.
4
+
1
5
### v0.7.1
2
6
- (Improvement) Tests generated by the `#[check(...)]` attribute now verify that there are no columns that exist in the schema but not in the model. (Previously, it only checked in one direction - verifying that all fields of the model existed in the schema.)
3
7
- (Improvement) The `sql_enum` macro now accepts an optional `Type` parameter that can be used to specify the discriminant type. By default, `i64` is still used.
/// | Unit/ZST struct | `struct Unit;` or `struct Unit {}` | ✘ |
12
13
/// | `enum`s | `enum Direction { Up, Down }` | ✘ |
@@ -64,7 +65,7 @@
64
65
///
65
66
/// More specifically, the generated test verifies that:
66
67
/// - The specified table exists.
67
-
/// - All specified columns/fields exist.
68
+
/// - The columns in the schema match up with those specified by the model type. If the model has fields not present in the schema (or vice versa) the test will fail.
68
69
///
69
70
/// It does *not* verify the validity of column types, nor does it test actual insertion/retrieval.
70
71
///
@@ -86,6 +87,32 @@
86
87
///
87
88
/// In both cases `T` is the type of the field being annotated. For some types (e.g. `PathBuf`) you may also be able to use a type it derefs to, like `Path`.
0 commit comments