mirror/TinyORM
1
0
Fork 0
mirror of https://github.com/silverqx/TinyORM.git synced 2025-12-30 15:29:36 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs fixtypo and revisited section

Browse Source 
[skip ci]
This commit is contained in:
silverqx
2023-07-25 08:44:04 +02:00
parent 7860dcd1bc
commit d98ee5c6c5
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/tinyorm/getting-started.mdx
View File

@@ -257,7 +257,7 @@ To create unix timestamp columns using the [tom migrations](/database/migrations
##### Custom timestamp column names
If you need to customize the names of the columns used to store the timestamps, you may define `CREATED_AT` and `UPDATED_AT` private getter methods on your model:
If you need to customize the names of the columns used to store the timestamps, you may define `CREATED_AT` and `UPDATED_AT` private static getter methods on your model:
#include <orm/tiny/model.hpp>

6
docs/tinyorm/relationships.mdx
View File

@@ -700,16 +700,16 @@ Do you see the confusing part? In short, if defining the `User::roles()` relatio
The same is true for the basic `Pivot` model, if you are using a basic pivot model and not a custom pivot model you still need to add the `Pivot` type to the `AllRelations` template parameter pack on the `Model` class!
The reason for all of this is so that the `Model` knows how to generate a `std::variant` to hold the pivot model in the `Model::m_relations` data member hash map, which you get using the `Model::getRelationValue` or `Model::getRelation` methods.
The reason for all of this is that the `Model` knows how to generate and work with the `std::variant` that holds the pivot model in the `Model::m_relations` data member map, then you can get the pivot model using the `Model::getRelationValue` or `Model::getRelation` methods.
##### User Data Members on Custom Intermediate Table Models
This is another nonstandard part of the custom pivot models. The `u_connection` and `u_timestamps` user data members and the `CREATED_AT` and `UPDATED_AT` static data members are ignored when obtaining pivot records from the database during the lazy or eager loading.
This is another nonstandard part of the custom pivot models. The `u_connection` and `u_timestamps` user data members and the `CREATED_AT()` and `UPDATED_AT()` static getter methods are ignored when obtaining pivot records from the database during the lazy or eager loading.
Let's describe how these data members are resolved:
- `u_connection` - inferred from the parent model
- `u_timestamps` - true if obtained attributes contain both the `CREATED_AT` and `UPDATED_AT` attributes
- `u_timestamps` - true if obtained pivot attributes contain both the `CREATED_AT` and `UPDATED_AT` attributes
- `CREATED_AT`, `UPDATED_AT` - inferred from the parent model, can be overridden using the `withTimestamps()` method
All these data members are taken into account normally when you call the `create`, `save`, `update`, ... on the Custom Pivot models!