So I tested the migration feature and string to list:string doesn't work. So we are left with the fact that a list:string field with IS_IN_SET multiple=False will not select the current value in an SQLFORM.
Seems kind of like a bug to me, does anyone else think so? On Tuesday, January 7, 2014 8:08:13 PM UTC-5, User wrote: > I have the same problem as the original poster. I am only storing a > single value as of now but I'm using list:string instead of string so that > if I change my mind to allow multiple values it will be easier to > transition. Is this a bug that it won't preselect the selected value? > Alternatively, does migration from a string field to a list:string field > preserve the string data? > > > On Monday, October 10, 2011 7:20:46 PM UTC-4, Anthony wrote: > >> On Monday, October 10, 2011 6:01:49 PM UTC-4, Cliff wrote: >>> >>> Mostly fixed now. There was also a bug in my controller code that was >>> complicating things. >>> >>> One problem remains. With readonly=True, the field still shows the >>> dictionary key rather than the value. >>> >> >> With readonly, I guess it's not using the widget, so it will just show >> the value stored in the field itself. Maybe you can define a represent >> function for the field so it shows the label associated with the value. >> >> Anthony >> > -- 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/groups/opt_out.
