yep, in a "programmatic" way cause *format* can be any callable in the
world of the developer mind, but basically the idea is the same.
On Tuesday, March 12, 2013 9:54:53 PM UTC+1, Alex Glaros wrote:
>
> like de-normalized?
>
> On Tuesday, March 12, 2013 1:41:29 PM UTC-7, Niphlod wrote:
>>
>> it's a table that is "close to the original", in this case with all
>> columns filled directly with the representation of the eventual foreign key
>> of the original one.
>>
>> On Tuesday, March 12, 2013 9:23:55 PM UTC+1, Alex Glaros wrote:
>>>
>>> what is a "shallow copy table"?
>>>
>>> Alex Glaros
>>>
>>> On Sunday, March 10, 2013 6:50:56 PM UTC-7, 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
