Skip to content

Use default dataset id #78

Closed
Closed
Use default dataset id#78
Assignees
pcostell
Labels
🚨This issue needs some love.api: datastoreIssues related to the Datastore API.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Datastore Stable

Description

@pcostell
pcostell
opened on Aug 1, 2014

Datastore will normalize keys without datasets to use the dataset of the app issuing the request. This should be preferred over hand crafting the app id from the dataset id by assuming a prefix of s~. Instead, leaving the key's datasetId blank will always get the correct dataset.

Activity

  1. rakyll
    added
    bug
    on Aug 1, 2014

  2. rakyll commented on Aug 1, 2014

    @rakyll
    rakyll
    on Aug 1, 2014
    Contributor

    Related to #13.

  3. pcostell commented on Aug 1, 2014

    @pcostell
    pcostell
    on Aug 1, 2014
    ContributorAuthor

    Ah exact duplicate, my bad.

  4. pcostell
    closed this as completedon Aug 1, 2014
  5. jgeewax
    added
    api: datastoreIssues related to the Datastore API.
    on Feb 2, 2015
  6. jgeewax
    added this to the Datastore Stable milestone on Feb 2, 2015
  7. yoshi-automation
    added
    triage meI really want to be triaged.
    🚨This issue needs some love.
    on Apr 6, 2020
  8. JustinBeckwith
    assigned
    pcostell
    on Feb 1, 2021
  9. chingor13
    added a commit that references this issue on Aug 26, 2022

    build(node): update client library version in samples metadata (#1356) (

    d374555
  10. chingor13
    added a commit that references this issue on Sep 13, 2022

    build(node): update client library version in samples metadata (#1356) (

    5b2f7cb
  11. sofisl
    added a commit that references this issue on Sep 16, 2022

    test: remove appveyor config (#78)

    facd10c
  12. sofisl
    added 3 commits that reference this issue on Oct 5, 2022

    test: remove appveyor config (#78)

    c10484d

    test: remove appveyor config (#78)

    c891a44

    Update CI config (#78)

    3e76813

  13. 73 remaining items

  14. sofisl
    added a commit that references this issue on Feb 25, 2026

    Indicate userProject is string, not boolean (#78)

    64c1d80
  15. GautamSharda
    added a commit that references this issue on Feb 25, 2026

    chore: release 2.2.0 (#78)

    f164707
  16. codyoss
    added a commit that references this issue on Mar 5, 2026

    build: ignore googleapis.com in doc link check (#78)

    3588407
  17. sofisl
    added 2 commits that reference this issue on Mar 5, 2026

    chore: release main (#78)

    28791a5

    Enable no-var in eslint (#78)

    a26c28a
  18. GautamSharda
    added a commit that references this issue on Mar 11, 2026

    chore: removing node7 job from CircleCI (#78)

    0752de7
  19. codyoss
    added a commit that references this issue on Mar 12, 2026

    chore: regenerate synth.metadata (#78)

    0ce6778
  20. GautamSharda
    added 3 commits that reference this issue on Mar 12, 2026

    chore(deps): update dependency @types/sinon to v7 (#78)

    06f4f07

    chore(deps): update dependency @types/sinon to v7 (#78)

    c48a079

    chore: es6ify service.ts (#78)

    702e499
  21. thiyaguk09
    added a commit that references this issue on Mar 18, 2026

    Indicate userProject is string, not boolean (googleapis#78)

    9a68c04
  22. GautamSharda
    added 2 commits that reference this issue on Mar 23, 2026

    fix: do not require projectId in custom envs (#78)

    4dac0af

    fix: do not require projectId in custom envs (#78)

    bf63f34
  23. shivanee-p
    added a commit that references this issue on Mar 27, 2026

    fix: do not require projectId in custom envs (#78)

    e6f8b2d
  24. thiyaguk09
    added a commit that references this issue on May 5, 2026

    fix: do not require projectId in custom envs (googleapis#78)

    36d9356
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: datastoreIssues related to the Datastore API.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions