About the latest release (1.2.4)

[Emilien Klein]

Is it just me or does it seem that this new release adds
functionalities that don't seem to be on the list of that many people?

The 3 issues that are linked to from http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes
for release 1.2.4 were starred by respectively 2,1, and a whopping 5
persons! Making the assumption that these are all different people,
that means that 8 persons have directly asked for these
improvements...

I'm not criticizing the release, just questioning the priorities...
It's nice to somewhat improve the queries and the Remote API, but
aren't there other features that seem to be much more urgent? What
happened to the important points of the Roadmap to be done around June
2009, if I remember well? http://code.google.com/intl/fr/appengine/docs/roadmap.html
Quite a lot of the things on this page seem to be much more urgent
than what's just been released...

Or maybe am I just asking too much???

[johntray]

I'm with you. 1.2.4 is a big disappointment.

On Aug 6, 9:38 pm, Emilien Klein <emilien.kl...@gmail.com> wrote:
> Is it just me or does it seem that this new release adds
> functionalities that don't seem to be on the list of that many people?
>

> The 3 issues that are linked to fromhttp://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

> for release 1.2.4 were starred by respectively 2,1, and a whopping 5
> persons! Making the assumption that these are all different people,
> that means that 8 persons have directly asked for these
> improvements...
>
> I'm not criticizing the release, just questioning the priorities...
> It's nice to somewhat improve the queries and the Remote API, but
> aren't there other features that seem to be much more urgent? What
> happened to the important points of the Roadmap to be done around June

> 2009, if I remember well?http://code.google.com/intl/fr/appengine/docs/roadmap.html

[nebulabug]

Can somebody explain more no

# Composite indexes no longer required for certain types of key
queries.
# Enhancement to SearchableModel allowing multiple properties to be
indexed.

[Alkis Evlogimenos ('Αλκης Ευλογημένος)]

On Fri, Aug 7, 2009 at 1:00 PM, nebulabug <sair...@gmail.com> wrote:

Can somebody explain more no

# Composite indexes no longer required for certain types of key
queries.

Example queries:

db.MyModel.all().ancestor()

This doesn't need an ancestor index anymore since ancestors are stored in the key.

db.MyModel.all().ancestor().filter('__key__ >', ...)

Likewise.

--

Alkis

[johnP]

Were there any changes on the production server that would cause the
datastore_cache recipe to stop working?

http://appengine-cookbook.appspot.com/recipe/seamless-memcache-caching-of-all-entities

johnP


On Aug 7, 1:14 pm, Alkis Evlogimenos ('Αλκης Ευλογημένος)
<evlogime...@gmail.com> wrote:

[johnP]

To clarify -

The datastore_cache recipe *did* stop working. It seems that the only
call that's getting passed-through to the wrapped stub is CreateRPC -
this is a newly-introduced method - and the recipe does not have a
method handle this call.

How to make it work is several levels beyond my level of
comprehension:) If anyone has some pointers as to how to make it
work, I (and many developers) will be thankful:) This is such a super-
valuable recipe...

Also - is there a way to make it more future-proof?

Thanks!

johnP

http://appengine-cookbook.appspot.com/recipe/seamless-memcache-caching-of-all-entities

On Aug 7, 1:21 pm, johnP <j...@thinkwave.com> wrote:
> Were there any changes on the production server that would cause the
> datastore_cache recipe to stop working?
>

> http://appengine-cookbook.appspot.com/recipe/seamless-memcache-cachin...

[GenghisOne]

I'm curious...did this latest release address the crippled full-text
search issue?

On Aug 10, 8:13 pm, johnP <j...@thinkwave.com> wrote:
> To clarify -
>
> The datastore_cache recipe *did* stop working.  It seems that the only
> call that's getting passed-through to the wrapped stub is CreateRPC -
> this is a newly-introduced method - and the recipe does not have a
> method handle this call.
>
> How to make it work is several levels beyond my level of
> comprehension:)  If anyone has some pointers as to how to make it
> work, I (and many developers) will be thankful:)  This is such a super-
> valuable recipe...
>
> Also - is there a way to make it more future-proof?
>
> Thanks!
>
> johnP
>

> http://appengine-cookbook.appspot.com/recipe/seamless-memcache-cachin...