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
I am using a single table structure, which means most of the the primary keys in my table have some kind of indicator of what type they are, so that it is possible to query them. An example from AWS Re:invent can be seen here: https://www.youtube.com/watch?v=DIQVJqiSUkE&t=2128s.
This does however not mix very well with how dynamoose searches for items, as the set is not called before fetch. It seems like the same problem arises with update, probably because of the same reason. That leaves me with a lot of queries looking like the example under general.
@MaximilianSchon Adding this to the v3 planning (#1040). One thing I'm planning on working on is having a Model represent a type of data as opposed to a DynamoDB table. Which should also help this as well. But ensuring get and set get called on all methods is important as well.
MaximilianSchon
changed the title
[FEATURE] Call set on search fields in query/get/delete/scan/update(?)
[FEATURE] Call set on search fields in query/get/delete/scan/update
Feb 1, 2021
Summary:
I am using a single table structure, which means most of the the primary keys in my table have some kind of indicator of what type they are, so that it is possible to query them. An example from AWS Re:invent can be seen here: https://www.youtube.com/watch?v=DIQVJqiSUkE&t=2128s.
This does however not mix very well with how dynamoose searches for items, as the set is not called before fetch. It seems like the same problem arises with update, probably because of the same reason. That leaves me with a lot of queries looking like the example under general.
Code sample:
Schema
Model
General
Other:
The text was updated successfully, but these errors were encountered: