it seems that `try-except` catches key/attribute error while evaluating
field.virtual and if it happens - doesn't create field.virtual at all
On Monday, May 9, 2016 at 7:17:07 PM UTC+3, Val K wrote:
>
> all a little differently:
> Field.Virtual('alias_name', lambda row: *None*) #- works OK! i.e.
> row.alias_name
> *exists* and row.alias_name == *None*
> *but *
> Field.Virtual('alias_name', lambda row: row.*bla_bla*) #- causes that row.
> alias_name *doesn't* *exist at all!*
>
>
>
> On Monday, May 9, 2016 at 7:05:27 PM UTC+3, Leonel Câmara wrote:
>>
>> Well the thing is
>>
>> row.*neverhood_will_be_processed_without_any_errors*
>>
>> Doesn't cause any error because row just returns None for values that
>> aren't there so the virtual field will just have None as the value. I do
>> agree it is sort of counter-intuitive that you have to be explicit about
>> the table for Virtual fields when you don't have to almost anywhere else.
>>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
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/d/optout.
