entries
.
If present, any matching key inside this dictionary will override the
inferred type of that particular entry. The explicit_types dictionary
can also specify if a field is mutable via a ‘mutable’ boolean flag
and if a field is unique via a ‘unique’ boolean flag:
Bearer <token>
, where <token>
is your auth token.explicit_types
dictionary is present, its values will override the inferred types of the entries. The explicit_types dictionary can also specify if a field is mutable via a ‘mutable’ boolean flag, or unique via a ‘unique’ boolean flag. For enum types, use the EnumType model with ‘values’ list and optional ‘restrict’ flag. Omit ‘values’ to create an open enum (auto-seeding). For contexts with nested unique IDs, parent ID values for the leftmost N-1 unique columns can be supplied as normal param keys. The rightmost column is always auto-incremented. For example, if unique columns are [‘user’, ‘session’, ‘step’], you can provide ‘user’ and ‘session’ values in params, and ‘step’ will be auto-generated.explicit_types
dictionary is present, its values will override the inferred types of the entries. The explicit_types dictionary can also specify if a field is mutable via a ‘mutable’ boolean flag, or unique via a ‘unique’ boolean flag. For enum types, use the EnumType model with ‘values’ list and optional ‘restrict’ flag. Omit ‘values’ to create an open enum (auto-seeding). For contexts with nested unique IDs, parent ID values for the leftmost N-1 unique columns can be supplied as normal entry keys. The rightmost column is always auto-incremented. For example, if unique columns are [‘user’, ‘session’, ‘step’], you can provide ‘user’ and ‘session’ values in entries, and ‘step’ will be auto-generated.