I do not know. but the slowdown is not storing and retrieving the list. the slowdown will be in populating the dropbox. 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.
You cannot even use ajax autocomplete because gae does not allow search of substrings. 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: > Thanks Massimo. > > > > > db.define_table("Player", > > SQLField("name", "string")) > > > db.define_table("Team", > > SQLField("name", "string"), > > SQLField("player_ids", "text")) > > > db.define_table("Match", > > SQLField("ground", "string"), > > SQLField("result", "string"), > > SQLField("team_ids", "text")) > > This looks very close to what I want. I guess even google will be using > something like this internally. I will take 1.55rc3 & give it a try. btw > will it be fast enough if I have large no of records in match & player table > (yes I cache them & read/write ratio will be around 80:1) > > Sudhakar.M --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
