This is very promising! Are you saying that this reference collection
query should work (note the named collection)?
class Foo(db.Model):
prop1 = db.IntegerProperty()
class Fee(db.Model):
my_foo = db.ReferenceProperty(Foo, collection_name='my_collection')
prop2 = db.IntegerProperty()
foo
On Mar 4, 9:11 am, Devel63 wrote:
> It is indeed a more complex query, and the IN values are keys. At one
> point, I had tried to make them key values in a named reference
> collection, but while the data store never complained, it never
> returned any results.
understood. happily, for the purp
It is indeed a more complex query, and the IN values are keys. At one
point, I had tried to make them key values in a named reference
collection, but while the data store never complained, it never
returned any results.
Can you confirm that it is impossible to make an entity query that
filters b
On Mar 1, 2:13 pm, Andy Freeman wrote:
> > However, when I do this, the dev_server creates a bunch of index
> > definitions, so that I have one with 1 property if there's 1 value in
> > the IN set, 15 index properties if there are 15 values in the IN set,
> > and so on.
>
> Are all of these index
> However, when I do this, the dev_server creates a bunch of index
> definitions, so that I have one with 1 property if there's 1 value in
> the IN set, 15 index properties if there are 15 values in the IN set,
> and so on.
Are all of these index properties necessary in production? Will a
produc
