Why simplejson instead of pickle?
On Oct 27, 10:26 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> The JSON bit was primarily to work around the 1000 item result set
> limit. Since simplejson already exists on appengine, was just easier
> for me to use json to store those data sets that grow beyond 1000
> entities and the convert them to dictionaries to parse.
>
> On Oct 27, 10:40 am, "Paul Kinlan" <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi,
>
> > JSON might work, but it is probably overkill. I was planning on maintaining
> > an inverted index like structure and do some simple set based operations on
> > the data, a ListProperty would have been ideal as AFAIK the data has its
> > order maintained in the list and searching the list would have been quite
> > efficient.
>
> > The 1000 item result set is quite limiting too.
>
> > Paul.
>
> > 2008/10/27 [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>
> > > My workaround for a case like this, as suggested by another member of
> > > this group, was TextProperty with JSON encoded data.
>
> > > On Oct 27, 10:25 am, "Paul Kinlan" <[EMAIL PROTECTED]> wrote:
> > > > Hi,
>
> > > > Thanks for the information. It is good to know. For what I need I
> > > > potentially need more than 5000 items so I will probably have to think
> > > of
> > > > another way of doing it.
>
> > > > Cheers and Thanks,
> > > > Paul
>
> > > > 2008/10/27 Waldemar Kornewald <[EMAIL PROTECTED]>
>
> > > > > Hi Paul,
>
> > > > > On Oct 26, 9:49 pm, "Paul Kinlan" <[EMAIL PROTECTED]> wrote:
> > > > > > Is the limit to the number of items in a ListProperty 1000? I ask
> > > > > because
> > > > > > the limit to the number of results in a Query is 1000 and if the
> > > > > > data
> > > in
> > > > > the
> > > > > > list is stored as seperate entities in the index I am assuming that
> > > this
> > > > > > means that the limit is 1000 as per the query guidelines.
>
> > > > > The limit is 5000 index entries per entity. So, if you have a
> > > > > StringProperty and a ListProperty you can put 4999 items into the
> > > > > list. The problem just seems to be that put() consumes *lots* of
> > > > > mcycles if your entity needs many index entries. I don't know if
> > > > > that'll change and how much we'll get charged for it.
>
> > > > > Bye,
> > > > > Waldemar Kornewald- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
