just to follow up on a pending question back a few months ago. When
the java datastore export will be
available?
On Dec 18 2009, 2:47 am, Jorge athenas...@gmail.com wrote:
I second this question.
Jorge Gonzalez
On Dec 2, 1:19 pm, king kingalpha...@gmail.com wrote:
Jason, do you have
I second this question.
Jorge Gonzalez
On Dec 2, 1:19 pm, king kingalpha...@gmail.com wrote:
Jason, do you have a timeline for when:
1. the cursor feature will be available?
2. the data download feature be available for JAVA (not Python).
On Oct 21, 10:54 am, Jason (Google)
can anyone shine some lights on when the java datastore export will be
available?
On Dec 2, 11:19 am, king kingalpha...@gmail.com wrote:
Jason, do you have a timeline for when:
1. the cursor feature will be available?
2. the data download feature be available for JAVA (not Python).
On Oct
Please check this out. You should be able to do queries returning greater
than 1000 rows. Obviously we have to work with google bigtable constraints
of 1000 rows etc. But our product does incremental queries to get you
desired results.
http://www.cloud2db.com
On Thu, Dec 17, 2009 at 6:12 PM,
Jason, the problem with the increment a counter on your own trick is
that would be in a separate Transaction and thus, unreliably linked to
the first insert Transaction right?
Also, the Stats hook mentioned above is NOT realtime is it? I believe
I read it is updated at least once a day.
On Oct
The query restrictions are an artifact of the way App Engine's datastore is
constructed, which makes certain operations (e.g. queries and reads) very
fast and scalable but does limit the types of queries you can make, though
you can typically get around these restrictions by re-thinking your model
