it's a problem on how to make it work without being heavily limited
performance-wise.
Having a custom format almost kills the possibility to fetch those records
using an "automatic" join with the referenced table.
It's one thing to fetch for every page the representation of the record for
10 rows, it's a totally different thing have to search through potentially
thousands of records with everyone's ultra-custom formatter....
If you need your users to scan the table "ala fulltext", don't use
references and formats: prepare a shallow copy table with real-text fields
instead of references.
On Monday, March 11, 2013 2:50:56 AM UTC+1, Cliff Kachinske wrote:
>
> I define a table so:
> db.define_table ('mytable', blah..., format='% (name) s')
>
> So as we know, grid will display the contents of the name field when
> mytable is used as a foreign table.
>
> But if you try to search on that field, the search only works if you
> submit record id integers as search parameters.
>
> Since human users don't generally know the record id or ids, this makes
> the search function less useful than it could be.
>
> Has anyone worked around this? If so, can you share your solution?
>
> Thanks, Cliff Kachinske
>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
