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
{{ message }}
Repository navigation
dataset.save() should work with entities using the new datastore.KEY symbol #1803
This worked because datastore.save's parameter and the object gotten from datastore.get had the same structure, but now datastore.save has to be called with {key:<key>,data:<data>}, it's more difficult to do simple updates to entities. Right now we have to do this:
Personally I preferred the old version where everything was {key:<key>,data:<data>} because it was more straightforward and didn't require a reference back to the datastore object, but if it's going to be changed it should at least be consistent across the board.
Activity
stephenplusplus commentedon Nov 17, 2016
Makes sense, thanks for the suggestion. PR sent: #1804
feat: Add `OR` query support (#1803)
fix: fixed typo (#1803)
fix(deps): update dependency @google-cloud/precise-date to v4 (#1803)
chore(main): release 4.0.1 (#1804)
fix(deps): update dependency @googleapis/iam to v16 (#1803)
fix(deps): update dependency proto3-json-serializer to ^3.0.2 (#1803)
fix: fixed typo (googleapis#1803)
chore(main): release 4.0.1 (#1804)