Comments (2)
Hey @patrickquigley102 👋
Great question, and I am glad you have found the library so helpful!
The short of the long is that it is not currently a feature because it is not an available operation via the DymamoDB DocumentClient. Ultimately it could be a feature, though behind the scenes it would ultimately be syntactic sugar for multiple requests. I suspect that is also what the SQL you shared is also doing when it's exectuted.
That said, not to leave you empty handed, here is how I would begin to implement something like that. The difficultly with abstracting away multiple calls is that you have to start making hard decisions around pagination, handling partial failures, ordering, and more. That's is usually why I try to keep ElectroDB out of the business of making decisions for the user on when to make more than one request; what is helpful for one use-case can be a total arm-bar to another use-case.
Let me know if this helps!
from electrodb.
Hey.
Thanks for the information 🙂. That's helpful.
start making hard decisions around pagination, handling partial failures, ordering, and more.
Aye, this is what I fear. And was hoping you'd already done it 😂.
And it makes sense to keep it out of ElectroDB,.
I'll likely redesign the single table to meet the access patterns within ElectroDB's features. or change the requirements to fit the current limitation I've built.
from electrodb.
Related Issues (20)
- Update nested Map value using set() method. HOT 2
- Incorrect key generated when using composite operation on patch/update HOT 3
- Doc example incorrect and misleading HOT 3
- Examples for adjacency lists and Materialized graphs
- Empty Collection to work with "Service" construct HOT 1
- Simplest implementation of unique constraint for non-key attributes HOT 1
- Support for BigInt HOT 9
- Created items not returned when using a transaction HOT 2
- Handling unstructured maps HOT 5
- ReturnValuesOnConditionCheckFailure is not available for non-transactional operations HOT 6
- Collection validation should check `field` property of composite attributes HOT 1
- Setter not triggered on removing a watching attribute HOT 1
- feature: support async getters/setters HOT 2
- Error: Cannot find module '@aws-sdk/lib-dynamodb/dist-cjs/commands/utils' HOT 6
- unmarshallOutput issue with @aws-sdk/lib-dynamodb
- Bug: apply `default` on upsert only for new items HOT 2
- Item update FAILS - error message contains broken link - need help / would like to fix docs HOT 1
- Collections issue : Trying to query across entities using collections but getting error HOT 2
- Is this a feature or a bug? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from electrodb.