new __key__ indexes, which I didn't think I needed, but they get
generated anyways from the auto-generate-indexes code.
Thanks,
Clay
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng
I've posted this to the issue tracker, which is probably more
appropriate place.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send
I was one of the ones who starred C# support since C# has LINQ. LINQ
gives you joins and aggregations, two features that are really needed
in the app engine.
C# is a serious request.
On Oct 6, 10:04 am, Kenneth goo...@kmacleod.ie wrote:
I was looking at the issue list the other day. There is
Whoops, this posted twice. I posted once, and didn't see it for
hours, so I posted basically the same message.
On Sep 29, 2:55 pm, clay clay.lenh...@searchlatitude.com wrote:
The death of normalization is premature. I wouldn't drink the
denormalization coolaid yet.
Sure joins are difficult
The death of normalization is premature. I wouldn't drink the
denormalization coolaid yet.
Sure joins are difficult in GAE, and disk space is cheap, however when
you change one atomic value in a denormalized database, you'll have to
change many rows, which itself can be slow, especially in GAE.
This is said because the datastore has cheap diskspace and there isn't
good support for joins here.
However, we'll relearn why normalization is good.
Denormalization means that what would normally modify a single cell
will have to modify many rows. This isn't ideal in a relational
database,
in JDO.
Cheers,
Clay
On Sep 23, 11:02 am, datanucleus andy_jeffer...@yahoo.com wrote:
BigTable simply is not a relational db, so it is highly misleading to
fake a relational wrapper and to me it caused lots of pain.
Apart from the fact that JDO is not a relational wrapper. The API
Jason,
Just to clarify, the exception happens *during* the commit, and then
succeeds. There isn't a way to rollback at this point.
I do believe there is a bug in the commit() method that you guys might
want to look at.
(FYI, my issue is resolved by other means).
Cheers,
Clay
On Sep 21, 7
A Google guy responded to a similar question:
We have no limits :)
Are they talking about 1TB, 10TB, 100s TB?
We would want to work with them to ensure their data moves on smoothly
and that their app has enough storage allocated, but there are no
practical limits.
Based on the documentation,
a larger default timeout?
Also, can you rollback on timeout?
Cheers,
Clay
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java
For the curious, below is the stacktrace:
It only takes about 3 seconds to report failure (but succeed):
Uncaught exception from servlet
com.google.appengine.api.datastore.DatastoreTimeoutException: Unknown
at
com.google.appengine.api.datastore.DatastoreApiHelper.translateError
That did it!! Thanks Jason!
On Sep 16, 11:24 pm, Jason (Google) apija...@google.com wrote:
Try adding the JARs to your build path without copying them to your lib
directory. Just use Add external JARs in the Eclipse Build Path dialog.
- Jason
Thanks Jason!
If you ever want to return to JDO ...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com
To
I'm getting an error when trying to filter on ANCESTOR IS locally in
Eclipse. Anyone know what might be the problem? Does anyone have a
working example? Am I forced to use the Low-Level API?
The code is:
PersistenceManager pm =
PMF.get().getPersistenceManager();
I got this working using the low-level API.
Actually, I'm not sure what JDO gives you over this. I wrap the low-
level Entity with my class and give it getters and setters. It
doesn't feel any more or less verbose.
--~--~-~--~~~---~--~~
You received this
15 matches
Mail list logo
