[web2py] How to use the new cache-options for referenced table by IS_IN_DB ?

2012-09-17 Thread Omi Chiba
I want to speed up to pull the referenced table by IS_IN_DB. For example, EDXUSF00 is referencing TDMUSJ00 table which takes 10 seconds to display the form because it has about 40,000 records. I was wondring if I can cache TDMUSJ00 so that it will be faster when the form is displayed second ti

Re: [web2py] How to use the new cache-options for referenced table by IS_IN_DB ?

2012-09-17 Thread Bruno Rocha
IS_IN_DB receives a cache parameter so you can do db.table.field.requires = IS_IN_DB(, cache=(cache.ram, 1800)) For that number of records I would use an ajax widget with endless scroll. (http://ivaynberg.github.com/select2/#infinite) --

Re: [web2py] How to use the new cache-options for referenced table by IS_IN_DB ?

2012-09-17 Thread Omi Chiba
Yeah ! It's about 5 seconds now !! On Monday, September 17, 2012 3:22:23 PM UTC-5, rochacbruno wrote: > > IS_IN_DB receives a cache parameter so you can do > > db.table.field.requires = IS_IN_DB(, cache=(cache.ram, 1800)) > > > For that number of records I would use an ajax widget with end

Re: [web2py] How to use the new cache-options for referenced table by IS_IN_DB ?

2012-09-17 Thread Massimo Di Pierro
IS_IN_DB is incharge of building the select(*options). How many options do you get in the form. It is possible most of the time is spent in rendering the form. Perhaps you should use requires = [IS_IN_DB()] # notice the [...] and the autocomplete widget. On Monday, 17 September 2012 15:36:1

Re: [web2py] How to use the new cache-options for referenced table by IS_IN_DB ?

2012-09-17 Thread Omi Chiba
Your're correct. I never use autocomplete widget before but I will try it! On Monday, September 17, 2012 4:21:20 PM UTC-5, Massimo Di Pierro wrote: > > IS_IN_DB is incharge of building the select(*options). How many options do > you get in the form. It is possible most of the time is spent in ren