On 1 Apr 2010, at 12:51, Jeff Schnitzer wrote:
In other words, Twig cannot perform the simple query:
Iterable<Object> foo = ofy.query().ancestor(yourobject);
All queries that are possible with the low-level datastore are
possible with Twig because there are low-level to type-safe "bridge"
methods. So you can simply do a typeless low-level ancestor query and
then get Twig to convert the resulting Entities into typesafe instances.
Quite frankly there just hasn't yet been the need to build un-typed
queries into the API. But if a good common use case arises then it
would fit in nicely to the FindCommand.
If you ever want to support something like this, you will need a
registration process.
That is a completely incorrect conclusion to jump to. As I said,
there actually was a very similar untyped query in the API that I
removed because it didn't seem so useful.
I am curious about what limitations Objectify has that makes this a
requirement. This thread (or this forum) is probably not the best
place to discuss the internal implementation details of future
features for Twig or Objectify so it might be better to take this
topic "offline".
If you ever want to support true polymorphic queries, you will need a
registration process.
Just wrong. What ever makes you claim that?
Don't claim this short-sightedness as a feature.
Think twice before posting replies at the end of a long day.
--
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-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
