We debated this quite a bit internally. To paraphrase the argument that
carried the day:
XG transactions are awesome but they are not true global transactions.
You're limited to 5 entity groups, you're more likely to see partially
applied transactions in global query results, you can get a
Ugh. Is this a correct further paraphrase?
* You wanted users to get exceptions which would force them to go to
the manual to figure out why they are getting exceptions.
There are less intrusive ways to force users into reading the manual!
I really hate software like this; it's a bozo bit that
On Oct 17, 11:05 pm, Max Ross (Google) max.r...@gmail.com wrote:
We debated this quite a bit internally. To paraphrase the argument that
carried the day:
XG transactions are awesome but they are not true global transactions.
You're limited to 5 entity groups, you're more likely to see
On Tue, Oct 18, 2011 at 9:07 AM, David Gay (Google) d...@google.com wrote:
One other consideration: XG transactions do not work on master/slave.
While the default could be different depending on whether HRD is used,
that definitely has drawbacks.
How can I detect if running on HRD vs M/S? I
This will tell you what type of datastore you are running against, but I
don't think it will help you in the development env:
http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/datastore/DatastoreService.java#388
On Tue, Oct 18, 2011 at 2:02 PM,
Yeah, unfortunately it seems permanently stuck at MASTER_SLAVE in
development mode. However, between this method for production and
manually trying to commit a transaction in development mode it looks
like I have a complete (but hacky) solution.
Thanks Alfred!
Jeff
On Tue, Oct 18, 2011 at 2:19
On Oct 15, 5:10 am, mscwd01 mscw...@gmail.com wrote:
Hey, the docs state:
There is currently no way to enable XG transactions for an individual
JDO or JPA transaction.
Instead you must enable XG transactions for the whole app. This is
fine but I'm wondering if this effects performance of
On Mon, Oct 17, 2011 at 9:38 AM, David Gay (Google) d...@google.com wrote:
Just enable it for the whole app: an XG transaction that touches only
a single entity group has exactly the same performance as a non-XG
transaction.
In that case, why is this a configurable setting?
Jeff
--
You
