Not possible to set the datastore namespace globally.

[theacodes]

Currently, gcloud.datastore.set_defaults lets you set the default dataset id, but doesn't let you set the default namespace. This means to use a namespace you have to be meticulous about setting in in every query, key, etc.

It'd be much easier if we are able to set the namespace at the dataset or connection level.

[dhermes]

Thanks @jonparrott

I had an eye on this a while back:

    In the future we will likely enable methods like

    - set_default_namespace

just haven't got to it. Given the discussion in #891 I'll hold off on fixing this until a client / Dataset approach is in place.

[jgeewax]

This is tricky -- I don't think set_default_namespace fixes the entire issue. I think it might be worth discussing another thin-wrapper like we did for Dataset, so the code we might write would be...

client = datastore.Client()
dataset = datastore.dataset('my-dataset-id')
namespace = dataset.namespace(customer_namespace_id)
company = namespace.get(namespace.Key('Company', 'google'))

Note that dataset wouldn't be required if you have the default set:

client = datastore.Client()
namespace = client.namespace(customer_namespace_id)
company = namespace.get(namespace.Key('Company', 'google'))

[dhermes]

When people use a namespace, they typically (in my experience, an overwhelming majority of the time) do it for an entire feature / section of a codebase, so

d = Dataset('foo', namespace='bar')

would be in one team's production code while

d = Dataset('foo', namespace='baz')

would be in another's.

This seems much more reasonable than having 3 classes to handle this scenario

Client -> Dataset -> Namespace

[jgeewax]

I like that. So the code an app would have would effectively be:

namespace = get_current_subdomain()
d = client.dataset('foo', namespace=namespace)
d.get(d.Key(...))

[dhermes]

Yes.

[theacodes]

This was resolved by moving to clients instead of having global methods.

[dhermes]

👍