Repository navigation
datastore: saveAll should not only return auto-inserted keys #17
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.triage meI really want to be triaged.I really want to be triaged.
Milestone
Description
Activity
- addedapi: datastoreIssues related to the Datastore API.Issues related to the Datastore API.
on Feb 2, 2015 - added🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
on Apr 6, 2020 - added 2 commits that reference this issue
on Aug 22, 2022 - added a commit that references this issue
on Sep 15, 2022 94 remaining items
- added a commit that references this issue
on Feb 25, 2026 - added a commit that references this issue
on Feb 26, 2026 - added 3 commits that reference this issue
on Mar 9, 2026 - added 2 commits that reference this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 18, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.triage meI really want to be triaged.I really want to be triaged.
datastore.saveAll only returns the newly inserted keys. For update operations, user may already provide a complete key. Return a mix of newly inserted and already-known keys in the associated order.