I guess I didn't expect to see mention of requiring entity groups for
transactions now that GAE supports cross-entity-group transactions.
Does GAE really need both modes?
Is there a performance benefit to not
enabling global transactions?
On Jan 13, 3:25 m, Ikai Lan (Google) ika...@google.com
A FYI about alternating versions for deployment to production...
Our build script names the version according data from SVN (GIT would
be similar), as a working copy (name = data and time), revision
(name=r123), or tag (name = tag name = our release version number).
Then the uploaded versions in
Sigh. No clue what else to do.
Anybody knows where else I can get some help?
On Jan 12, 9:53 am, Răzvan Rotaru razvan.rot...@gmail.com wrote:
Hi,
I'm trying to start a dev_appserver instance inside a running jvm. So I'm
doing:
DevAppServerFactory.createDevAppServer(new
One thing that would make this helpful would be the ability to
automatically delete old versions. The current limit of 10 versions
means I have to manually go through and delete old ones before I can
deploy new ones. It would be nice to automate a scrolling window of
versions.
Of course, not
Google has said in the past that there is no negative performance
effect from enabling XG transactions if you only use a single entity
group. The rational thing to do is always enable XG transactions all
the time, but be aware when you span multiple entity groups in a
transaction.
I think it was
Definitely very disappointing. And totally agree GAE would have a lot
to offer, if they could just fix that bug.
The good news is a lot of other folks are stepping in to fill that
easy one-click cloud deployment space!
Join us next month at http://OpenCFSummit.org to learn more!
On Jan 13,
I'm not sure, maybe its a lucky escape it shows how easy the rug is to
be pulled from underneath you.
I'll be there see you next month
A
On Jan 14, 11:17 am, Jason Blum jason.b...@gmail.com wrote:
Definitely very disappointing. And totally agree GAE would have a lot
to offer, if they could
