datastore: Allow non-transactional mode for datastore? #324

Activity

1. jgeewax

   added

   enhancement

   type: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.

   on Dec 6, 2014
2. jgeewax

   changed the title [-]datastore: Allow non-transactional mode for?[/-] [+]datastore: Allow non-transactional mode for datastore?[/+] on Dec 6, 2014
3. ryanseys commented on Dec 6, 2014

   

   ryanseys

   on Dec 6, 2014

   Contributor

   More actions

   This is just the dataset.save() method by default I'm pretty sure.
4. ryanseys commented on Dec 6, 2014

   

   ryanseys

   on Dec 6, 2014

   Contributor

   More actions

   That is, requests are non transactional by default and only when you call dataset.runInTransaction(function(transaction){}); are they requested in a transactional mode.
5. stephenplusplus commented on Dec 9, 2014

   

   stephenplusplus

   on Dec 9, 2014

   Contributor

   More actions

   ^ that's correct.

   The API docs for save describes how it uses upsert, insert, or update https://googlecloudplatform.github.io/gcloud-node/#/docs/v0.11.0/datastore/dataset?method=save and lookups are done with get: https://googlecloudplatform.github.io/gcloud-node/#/docs/v0.11.0/datastore/dataset?method=get
6. stephenplusplus

   closed this as completedon Dec 9, 2014
7. jgeewax

   added

   api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.

   on Feb 2, 2015
8. jgeewax

   added this to the Datastore Stable milestone on Feb 2, 2015
9. JustinBeckwith

   assigned

   stephenplusplus

   on Feb 1, 2021
10. chingor13

    added a commit that references this issue on Aug 22, 2022

    chore: release 3.1.0 (#324)

    ...

    79bb84b
11. sofisl

    added 4 commits that reference this issue on Oct 11, 2022

    chore: release 3.6.1 (#324)

    b46463e

    fix: update node issue template (#324)

    ...

    4ac69ee

    chore: release 1.2.1 (#325)

    ...

    f1e1854

    chore: release 3.6.1 (#324)

    67e7bd0
12. 27 remaining items

    Load more
13. GautamSharda

    added a commit that references this issue on Feb 2, 2026

    fix(deps): update dependency @google-cloud/logging to v5 (#324)

    0daa641
14. sofisl

    added a commit that references this issue on Feb 3, 2026

    Release v2.0.6 (#324)

    7a08061
15. GautamSharda

    added a commit that references this issue on Feb 3, 2026

    fix(deps): update dependency @google-cloud/logging to v5 (#324)

    202fb86
16. sofisl

    added 2 commits that reference this issue on Feb 4, 2026

    chore(deps): update dependency @google-cloud/common to v2 (#324)

    8ed7b17

    refactor: asyncify the system test (#324)

    a8878fe
17. GautamSharda

    added a commit that references this issue on Feb 5, 2026

    chore: test Restify 18 in the install tests (#324)

    c596ffe
18. sofisl

    added a commit that references this issue on Feb 17, 2026

    refactor: asyncify the system test (#324)

    c066c5a
19. GautamSharda

    added a commit that references this issue on Feb 23, 2026

    chore: test Restify 18 in the install tests (#324)

    b7462ad
20. sofisl

    added a commit that references this issue on Feb 24, 2026

    Making .dotChanges a method (#324)

    3441770
21. GautamSharda

    added 2 commits that reference this issue on Feb 25, 2026

    chore(main): release 3.4.0 (#324)

    c6e7896

    chore: test Restify 18 in the install tests (#324)

    e2384a7
22. GautamSharda

    added a commit that references this issue on Mar 5, 2026

    chore(deps): update dependency @google-cloud/pubsub to ^0.21.0 (#324)

    a148f77
23. codyoss

    added 2 commits that reference this issue on Mar 9, 2026

    chore(deps): update dependency sinon to v14 (#324)

    ...

    500e114

    chore(deps): update dependency sinon to v14 (#324)

    ...

    a4475bd
24. GautamSharda

    added a commit that references this issue on Mar 11, 2026

    refactor: use Object.assign where possible (#324)

    c28f31f