On Aug 13, 12:30 pm, "Zeeshan Mirza" wrote:
> You can perform the CURD operation by using GQL
No, you can't. You can perform R.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googl
: google-appengine@googlegroups.com
Date: Fri, 13 Aug 2010 03:39:57
To: Google App Engine
Reply-To: google-appengine@googlegroups.com
Subject: [google-appengine] Re: GQL Query
On Aug 11, 1:41 pm, Karan Malhotra wrote:
> whats the GQL
> i herad SQl
GQL is a limited subset of SQL that allows
On Aug 11, 1:41 pm, Karan Malhotra wrote:
> whats the GQL
> i herad SQl
GQL is a limited subset of SQL that allows you to write SQL-style
SELECT queries to get entities from the datastore. See
http://code.google.com/appengine/docs/python/datastore/gqlreference.html
--
You received this messa
On Aug 10, 9:57 pm, jp wrote:
> Hi
>
> Can anyone teach me how to do insert delete and update statement for
> GQL
>
> thanks in advance
You can't. GQL is SELECT-only, and is really only an interface for
SQL programmers to create queries using a more familiar interface than
db.Query.
--
You r
In the beginning of Appengine some objects got lost in the index.
The solution was get the object by key and put() it again.
This solved it for some people who where missing objects with a query
that has a filter.
If you don't know the key of the object, page over all keys of that
object type and
Hi phtq,
I've only had this problem once, and after deleting that record it never
occured again... The only reason I mentioned it, is because you started this
thread!
Jaap
On Wed, Aug 5, 2009 at 11:28 PM, phtq wrote:
>
> Hello Jaap,
>
> Sounds like this problem is not all that rare, although w
Hello Jaap,
Sounds like this problem is not all that rare, although we have never
hit it before in over a year of development on the app engine.
I can't relate the problem to anything we have done recently. I don't
think we have introduced any new indexes for a while for example.
I take it Goog
Same here, just good old ASCII chars in that record.
On Wed, Aug 5, 2009 at 12:55 AM, phtq wrote:
>
> The fact that the record can be retrieved with any 2 of the 3 filters
> indicates that there are no hidden characters.
>
> On Aug 5, 8:41 am, Wooble wrote:
> > Are you sure there isn't a space
The fact that the record can be retrieved with any 2 of the 3 filters
indicates that there are no hidden characters.
On Aug 5, 8:41 am, Wooble wrote:
> Are you sure there isn't a space or other non-printable character in
> your data in the datastore? It's certainly possible your index is
> corr
Are you sure there isn't a space or other non-printable character in
your data in the datastore? It's certainly possible your index is
corrupt, but I'd check for more likely causes first.
On Aug 4, 12:01 am, phtq wrote:
> In our application (kbdlessons version 1-01) we have just had a case
> wh
I've experienced a similar problem running on the SDK.aplying two filter()s
result in 0 records found. Aplying either one of the filter()s and comparing
the resultsets found a record that matches both filter()s.
Jaap Taal
[ Q42 BV | tel 070 44523 42 | direct 070 44523 65 | http://q42.nl |
Waldorp
I think I found it - didn't expect to get lucky so quickly...
class DummyData(db.Model):
x = db.StringListProperty()
y = db.StringProperty()
class Dummy(webapp.RequestHandler):
def get(self):
d = DummyData()
d.x = ['a','b','c']
d.y = 'test'
d
Thanks, Andy. You are correct, my mistake. I saw some strange behavior
with the data that I was working with and I couldn't figure why the
return values made sense for the query. There I had StringProperty
instead of TextProperty. I thought I will construct a quick example
and made the mistake of
Don't use in, just use equal:
q = db.GqlQuery("SELECT * FROM DummyData where x = 'c' and x = 'a'")
And you can read this document:
http://code.google.com/intl/zh-CN/appengine/docs/python/datastore/entitiesandmodels.html#Lists
2009/4/19 ecognium
>
> Hello everyone, I noticed an odd behavior with
db.TextProperty is not an indexable property. That means that it's
not queryable either.
It would be nice if to get an exception or some other indication of
what's going on.
However, note that "indexable" is something that happens in the
datastore when an instance is store. If you change a pro
On Mar 30, 7:44 am, Nick Winter wrote:
> I think what you're looking for is called full-text search and there
> isn't any way to do it on App Engine. You'll have to split the name
> into two properties.
to be fair, app engine does have full text search:
http://groups.google.com/group/google-app
I think what you're looking for is called full-text search and there
isn't any way to do it on App Engine. You'll have to split the name
into two properties.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App
thanks bryan & bill! yes, I was using GQL because I wanted to query
via the data viewer. the KEY('mykeystring') on the right-hand side
not working was throwing me off. that's good to know that it works in
the shell.
audrey
On Feb 27, 11:49 am, Bill wrote:
> Audrey,
>
> If for some reason, yo
Audrey,
If for some reason, you need to use GQL to lookup by key string
instead of using get() like Bryan suggested, you can use KEY
('mykeystring') instead of the raw string on the right-hand side of
your __key__ comparison. Full documentation is here:
http://code.google.com/appengine/docs/pyth
You don't actually need to use GQL, just use:
db.get('mykeystring')
On Feb 26, 9:21 pm, Audrey M Roy wrote:
> How do I write a GQL query that's something like this...
>
> SELECT * FROM Pet WHERE __key__='mykeystring'
>
> the above returns the error BadFilterError: invalid filter: __key__
> filt
In that case, you would not be able to do inequality filters on both dates.
You may be able to work around this by storing the start and end date in two
separate entities, and referencing one from the other. Then you can do one
inequality filter on the start date, and one on the end date.
-Marzia
Thanks. But as I said, I have two properties, a start and end date.
On Wed, Oct 22, 2008 at 2:11 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Date ranges shouldn't be a problem, as you can do multiple inequality
> filters with App Engine, as long as they are on the same property:
> ht
Hi,
Date ranges shouldn't be a problem, as you can do multiple inequality
filters with App Engine, as long as they are on the same property:
http://code.google.com/appengine/docs/datastore/queriesandindexes.html#Restrictions_on_Queries
-Marzia
On Tue, Oct 21, 2008 at 8:17 PM, Chris <[EMAIL PROTE
How do you query date ranges? Say I have an object with a start date
and end date. How do I query objects whose range falls on
date.today()?
On Aug 30, 4:45 am, fdezjose <[EMAIL PROTECTED]> wrote:
> I've found a solution to my case. I had to query on two properties:
> latitude and longitude, surf
I've found a solution to my case. I had to query on two properties:
latitude and longitude, surfing the net I discovered this thing called
Geohash (http://en.wikipedia.org/wiki/Geohash) so now I have a geohash
property that I can query without any problem.
This blog post was also useful:
http://l
I don't like this "Restrictions on Queries" :-(
On Aug 28, 10:26 pm, Nevin Freeman <[EMAIL PROTECTED]> wrote:
> From:http://code.google.com/appengine/docs/datastore/queriesandindexes.html
>
> "The query mechanism relies on all results for a query to be adjacent
> to one another in the index table
From: http://code.google.com/appengine/docs/datastore/queriesandindexes.html
"The query mechanism relies on all results for a query to be adjacent
to one another in the index table, to avoid having to scan the entire
table for results. A single index table cannot represent multiple
inequality fil
Why this limitation?
On Aug 28, 10:17 pm, Nevin Freeman <[EMAIL PROTECTED]> wrote:
> José,
>
> Many different workarounds are available, depending on your
> circumstances. The simplest (not ideal) thing to do would be to run
> two queries and then take the intersection of the two results, i.e.:
>
José,
Many different workarounds are available, depending on your
circumstances. The simplest (not ideal) thing to do would be to run
two queries and then take the intersection of the two results, i.e.:
q1 = Model.gql("WHERE prop1 < :1", number1)
q2 = Model.gql("WHERE prop2 > :1", number2)
batc
For your local application you can comment these checks :-)
if operator in self.INEQUALITY_OPERATORS:
if self.__inequality_prop and property !=
self.__inequality_prop:
raise datastore_errors.BadFilterError(
'Only one property per query may have inequality filters
(%s).
File "C:\Program Files\Google\google_appengine\google\appengine\api
\datastore.py", line 1077, in _CheckFilter
', '.join(self.INEQUALITY_OPERATORS))
BadFilterError: BadFilterError: invalid filter: Only one property per
query may have inequality filters (<=, >=, <, >)..
On Aug 28, 9:51 pm,
Only one? per query??
On Aug 28, 9:07 pm, fdezjose <[EMAIL PROTECTED]> wrote:
> Hello! I'm new in the App Engine world and I've run into an issue
> that's driving me crazy. I need to compare two properties (ex.
> propertyA > 4 AND propertyB > 8) But by doing that I've discovered
> that only one p
32 matches
Mail list logo
