I just tested this with a simple app using postgresql database and it seems that it doesn't quite work.
It appears it will leave the string data that exists in the string field alone in the database, however web2py will interpret it such that the first and last character are truncated. For example: "hello" -> "ell" "something" -> "omthin" "world" -> "orl" As soon as you add another list item to the string, then web2py will truncate the original string's first and last characters in the database in addition to adding the new item. Migration back from list:string to string will preserve whatever list:string data is there (in the web2py representation format). "hello", "world" -> "|hello|world|" "one", "two" -> "|one|two|" Would it make sense for the migration process to handle this more gracefully? On Monday, January 13, 2014 3:34:47 PM UTC-5, User wrote: > Does a migration from a 'string' field to a 'list:string' field preserve > string data that is already in the database and convert it to the format > required by list:string? > -- 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.
