-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for more than one Model #1
Comments
For example
Notice that both Model1 and Model2 wind-up sharing the same table name and schema. |
You are right and this has been heavily refactored in the next version, which has not been pushed to Github yet. |
Cool. Looking forward to the new version. Do you know about when that will drop? I'm trying to decide whether to make local modifications until then. |
I am unsure. This project was initially started to ease the transition from MongoDB to DynamoDB, which has been postponed. The next version has huge changes that were never pushed. Maybe I could push them on an alternate branch so you can try them out. |
Works for me. That'd be awesome. |
The branch is called vnext. Models now return instances of DynamoQuery. The tests are incomplete. |
Thanks! |
Integrating some more powerful schema validation with something like this https://www.npmjs.com/package/jsonschema could have been awesome. |
I've created two separate Model objects mapped to two different Dynamo tables.
When I'm done, both Models wind-up referencing the same Schema instance.
I think this is related to how prototypes are being used in model.js, but I'm not sure.
Is there something special I have to do to use more than one table with dynamodb-model?
The text was updated successfully, but these errors were encountered: