Yes, it looks like previously you could pass the name of a virtual field to the "fields" argument of SQLFORM, but it no longer works (you now have to use extra_fields). I'm not sure why this change was made, but I would say it does break backward compatibility.
Anthony On Wednesday, September 24, 2014 3:36:04 AM UTC-4, Donatas Burba wrote: > > Hello, everyone. I have a project running on web2py v2.9.5 and an form > where SQLFORM shows defined virtual fields. After trying to migrate to > v2.9.6 (even up to 2.9.11), I get error ticket in this form, because (if I > correctly understand) virtual fields are no more in table.fields list. > After examining source, I found a > commit bb13d6b7299d9dab9a64761c9427e3f2552dc6e9 which introduced > extra_fields attribute to SQLFORM constructor. So as I understand, if I > want show virtual fields after upgrade, I must somehow pass them in > extra_fields? In reality I won't do any changes that because there are too > much such places in the project, so it will be stick with v2.9.5. I really > love this framework, but unfortunately it isn't backwards compatible. Am I > right? > -- 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.
