On Jan 2, 9:21 am, mdipierro <[email protected]> wrote:
> I do not know. but the slowdown is not storing and retrieving the
> list. the slowdown will be in populating the dropbox.
The GAE datastore is pretty slow. From what I've gathered, depending
on your data model, if you're doing more than 2 read/writes (with
writes being *much* slower) per request, you'll probably have issues.
> Even wrose. The problem is GAE does not allow retrieving more than
> 1000 records at the time. This means that if you have more than 1000
> players and/or teams you are in trouble.
This turns out to be much less problematic than it sounds. Have
something unique that you're ordering the query by. Timestamp, ID,
whatever. Do a query, get 1000 records, do a second query and filter
it by ("orderField >", lastValue). (You might want to spread those
queries over multiple requests, though, because of the hefty CPU
limitations).
> You cannot even use ajax autocomplete because gae does not allow
> search of substrings.
"Cannot" is such an ugly word. There are always ways to do things,
but sometimes you have to get *really* creative.
> Assuming one player playes only for one team you can store the team
> with the player in the Player table not use a many2many between team
> and player.
>
> Massimo
>
> On Jan 2, 9:10 am, "sudhakar m" <[email protected]> wrote:
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
