"Nick Johnson (Google)"
wrote:
> Hi ecognium,
>
> On Tue, Jun 23, 2009 at 6:11 PM, ecognium wrote:
>
> > Thanks again - this is very helpful. I will let you know if i run into
> > any future index creation errors as it could have been caused by any
> > number
categ list at this
point (I guess the max will be 6C3 = 20 under such a situation). The
keyword list will be probably go into the 20s but do not see anything
beyond that and will always be used only once in the query.
Thanks,
-e
On Jun 23, 3:53 am, "Nick Johnson (Google)"
wrote:
>
ateg
- name: categ
- name: categ
- name: keywords
- name: __key__ # used for paging
Thanks,
-e
On Jun 22, 2:10 am, "Nick Johnson (Google)"
wrote:
> Hi ecognium,
>
> If I understand your problem correctly, every entity will have 0-4 entries
> in the 'categ'
n 22, 2:10 am, "Nick Johnson (Google)"
wrote:
> Hi ecognium,
>
> If I understand your problem correctly, every entity will have 0-4 entries
> in the 'categ' list, corresponding to the values for each of 4 categories
> (eg, Color, Size, Shape, etc)?
>
>
Hi All,
I would like to get your opinion on the best way to structure my
data model.
My app allows the users to filter the entities by four category types
(say A,B,C,D). Each category can have multiple values (for e.g.,
category type A can have values 1,2,3) but the
user can choose only one
Thanks Barry/Nick. I was not aware of either projects and looks like
the geomodel project will probably be a better fit for what I am
trying to do. I will try to integrate it to see if it works for me.
Thanks again!
On Jun 18, 2:51 am, "Nick Johnson (Google)"
wrote:
> Hi ecogniu
ache
and was just thinking about how the application itself is cached. It
makes more sense just to use memcache so I can control the process.
Thanks for your suggestion.
-e
On Jun 17, 3:09 am, "Nick Johnson (Google)"
wrote:
> Hi ecognium,
>
> On Wed, Jun 17, 2009 at 9:17 AM, ec
Hi All,
My application requires certain types of query features that are
not currently possible through Datastore API and so I am thinking of
moving the query side of things to Anazon's SimpleDB (mainly use it to
return keys). For example, I would like to return entities that are
within a cer
Thanks, Nick. It works!
On May 18, 5:00 am, "Nick Johnson (Google)"
wrote:
> Hi ecognium,
>
> You can do this by implementing the generate_key method in your
> bulkloader.Loader class. See the code for
> details:http://code.google.com/p/googleappengine/source/browse/tr
Hi All,
How do i specify a key name when using the bulk upload tool? I am
currently using WWW:: Mechanize to upload my data one row at a time
but would be nice if i can use the bulk loader as i don't want to
reinvent the many options available in the tool.
Thanks!
--~--~-~--~~
Thanks, Nick. You are right. I ran into some issues, which i tracked
it down to the key call but then I ended up testing the keys using
values '123' etc... So the BadKeyError is from my bad key request and
not unavailable key.
On May 13, 3:46 am, "Nick Johnson (Google)"
Hello Everyone,
It looks like Model.get(keys) raises an exception (BadKeyError)
when the key does not exist even though it is not mentioned here
http://code.google.com/appengine/docs/python/datastore/modelclass.html#Model_get.
On the other hand, Model.get_key_by_name(names) just returns None
Hello Everyone,
It looks like the images.resize() always honors the aspect ratio.
Is there a way to force a certain dimension? For example, in
ImageMagick you can use an exclamation (!) at the end to override the
aspect ratio Any suggestions will be appreciated.
Thanks!
--~--~-~--~
rty to TextProperty or the reverse, strange things will
> probably happen. (If you put some instances with StringProperty, I
> suspect that you can still successfully query for those instances
> using that property after you've switched to TextProperty.)
>
> On Apr
ces with StringProperty, I
> suspect that you can still successfully query for those instances
> using that property after you've switched to TextProperty.)
>
> On Apr 19, 1:24 am, ecognium wrote:
>
> > Hello everyone, I noticed an odd behavior with GQL query when
Hello everyone, I noticed an odd behavior with GQL query when it has
two IN operators and a regular condition. Below is some basic code to
reproduce the problem:
class DummyData(db.Model):
x = db.StringListProperty()
y = db.TextProperty()
class Dummy(webapp.RequestHandler):
16 matches
Mail list logo
