This is wrong:
<a href="./lookup?item={{=db.id}}">
The reason is that it would break if the path_info.count('/')!=2 in the
current page.
These two produce the same net effect:
<a href={{=URL('lookup', args=db.id)}}>
<a href="{{=URL('lookup', vars={'item':db.id})}}">
I would use args if 'lookup' GETs a persistent object that resides inDB and
I would use vars if it GETs the result of a computation and you are passing
imput parameters. Anyway, this is purely for aesthetic reasons.
On Tuesday, 21 March 2017 12:57:02 UTC-5, r wrote:
>
> <a href="./lookup?item={{=db.id}}">
>
> result: /lookup?item=1
>
>
>
> <a href={{=URL('lookup',args=db.id)}}>
>
> result: /lookup/1
>
>
>
> <a href="{{=URL('lookup', vars={'item':db.id})}}">
>
> result: /lookup?item=1
>
>
> Just wondering, is there any benefit from using one method over the
> others? I plan on retrieving the URL args/vars on the webpage. For me the
> 1st one seems like the simplest but no difference vs the 3rd. So why would
> people use the 3rd over the 1st when linking?
>
--
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.
