Capabilities will only be thrown at write time, so yes, it'll happen when
the object is flushed to the datastore. This has the other problem of you
having to do an extra write all the time - the majority of the time, you
will *not* be in a read-only mode and these will be wasted CPU cycles.
On Sat
Hey guys, quick question for a possible workaround to test if the
datastore is read only.
Could I just fetch an object and modify it at the beginning of my call
like:
Obj foo = pm.getObjectById(...)
try {
foo.setUnusedVariable(0);
} catch (CapabilityDisabledException e) {
// Datastore is read
Okay, thanks guys. I'll keep on the lookout for the next release.
On Jul 15, 7:50 pm, Don Schwarz wrote:
> This will be supported in Java in the next release.
>
> On Thu, Jul 15, 2010 at 6:10 PM, Ikai L (Google) wrote:
>
>
>
> > I'd appreciate if members of this group didn't "bump" topics - it c
This will be supported in Java in the next release.
On Thu, Jul 15, 2010 at 6:10 PM, Ikai L (Google) wrote:
> I'd appreciate if members of this group didn't "bump" topics - it creates
> noise, and we do make an effort to respond to topics, even older ones.
>
> There's capabilities API, unfortuna
I'd appreciate if members of this group didn't "bump" topics - it creates
noise, and we do make an effort to respond to topics, even older ones.
There's capabilities API, unfortunately, this is Python only for now.
http://www.slideshare.net/jasonacooper/strategies-for-maintaining-app-engine-avail
bump bump pump it up!
On Jul 8, 6:01 am, coltsith wrote:
> Is there a way to do this? I've like to be able to check if the data
> store is read only before I start all the work, rather than catch the
> CapabilityAPI exception.
>
> Thanks
--
You received this message because you are subscribed t
