Thanks for your reply! You are right, if we are talking about some application with full built-in logic and it would like to be independent on any DBEngine. But IMHO there are a lot of opposite situations: DB-App with many different clients. In this case VIEW is very helpful solution, it minimizes client's thickness and much safer. It'd be better have a choice, no?
P.S. I've solved my problem (1.5 lines of code), it works fine! -- 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.