You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to do a where clause to return a range of entities (i.e. "select * from metrics where _ _ key _ _ >=KEY(metrics,100) and _ _ key _ _ <= KEY(metrics,200)")
This is the error I get: _ _ key _ _ filter value must be a Key
I've tried simplifying to just "select * from metrics where _ _ key _ _ = KEY(metrics,100)" where I can see in the datastore viewer shows an id = 100.
I saw the other issue that said you can drop an entity right into it, but the full query might not know that an ID=100 exists or ID=200 exists, but there are probably ID=110 or 163.
I've tried with and without apostrophes on both 'metrics' and '100' without success.
Am I doing it wrong? Perhaps I shouldn't even be using ID like this? Perhaps the key in a where clause only be a precise value?
To be fair, I haven't yet tried this on GAE + datastore, should I expect different behavior?
The text was updated successfully, but these errors were encountered:
I want to do a where clause to return a range of entities (i.e. "select * from metrics where _ _ key _ _ >=KEY(metrics,100) and _ _ key _ _ <= KEY(metrics,200)")
This is the error I get: _ _ key _ _ filter value must be a Key
I've tried simplifying to just "select * from metrics where _ _ key _ _ = KEY(metrics,100)" where I can see in the datastore viewer shows an id = 100.
I saw the other issue that said you can drop an entity right into it, but the full query might not know that an ID=100 exists or ID=200 exists, but there are probably ID=110 or 163.
I've tried with and without apostrophes on both 'metrics' and '100' without success.
Am I doing it wrong? Perhaps I shouldn't even be using ID like this? Perhaps the key in a where clause only be a precise value?
To be fair, I haven't yet tried this on GAE + datastore, should I expect different behavior?
The text was updated successfully, but these errors were encountered: