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
-`join_model`: The model you want to join with (e.g., Tier).
757
+
-`join_prefix`: Optional prefix to be added to all columns of the joined model. If None, no prefix is added.
758
+
-`join_on`: SQLAlchemy Join object for specifying the ON clause of the join. If None, the join condition is auto-detected based on foreign keys.
759
+
-`schema_to_select`: A Pydantic schema to select specific columns from the primary model (e.g., UserSchema).
760
+
-`join_schema_to_select`: A Pydantic schema to select specific columns from the joined model (e.g., TierSchema).
761
+
-`join_type`: pecifies the type of join operation to perform. Can be "left" for a left outer join or "inner" for an inner join. Default "left".
762
+
-`kwargs`: Filters to apply to the primary query.
763
+
-`offset`: The offset (number of records to skip) for pagination. Default 0.
764
+
-`limit`: The limit (maximum number of records to return) for pagination. Default 100.
765
+
-`kwargs`: Filters to apply to the primary query.
766
+
767
+
709
768
#### More Efficient Selecting
710
769
For the `get` and `get_multi` methods we have the option to define a `schema_to_select` attribute, which is what actually makes the queries more efficient. When you pass a `pydantic schema` (preferred) or a list of the names of the attributes in `schema_to_select` to the `get` or `get_multi` methods, only the attributes in the schema will be selected.
0 commit comments