The problem is that when you autocomplete you may have lots of records
so search has to be done based on DB content. If you were to use
virtual fields (computed on the fly by web2py) the search would be
done client-side in memory. It would be faster but would not work for
large record sets.
Massim
Thanks Massimo, I can do that. Only slight issue is the computed
field physically takes space in the database.
I was a bit puzzled why a virtualfield would not work because I
thought it was introduced for precisely this kind of use.
--
D
On Aug 9, 1:54 am, mdipierro wrote:
> You must have comp
You must have computed field that contains the contend you want to use
'name + town'
On Aug 8, 7:06 pm, villas wrote:
> I have the following requirements:
>
> 1) The widget to show the 'name' but save the 'id'
> 2) The widget to reveal the fields 'name' plus 'town' in the drop down
> selection.
>
You did see the thread linked below? This autocomplete does actually
work. The arrow keys don't seem to work very well in IE8 but it's
easy to set up and worth trying.
http://groups.google.com/group/web2py/browse_thread/thread/dcbb1b8ee8fde952/d941cfea44e361c2?lnk=gst&q=autocompletion#d941cfea44
Here's another option:
http://www.web2pyslices.com/main/slices/take_slice/24
On Feb 20, 9:20 pm, weheh wrote:
> I'm in the middle of doing my first autocompletion. I've read and
> reread doc v2 example. But I've also gone to the jQuery site and
> looked at their example.
>
> Q1) Does anyone have
5 matches
Mail list logo
