I agree this is a bug. The problem is that this means our internal representation is ambiguous. We cannot fix this without changing the internal representation and breaking backward compatibility. Will think of a solution. Thanks for catching this.
On Wednesday, 29 November 2017 07:12:56 UTC-6, Scott Hunter wrote: > > Suppose I have a list:string field, and I put `A|B` in for one of the > elements. This works as expected, and gets represented internally as > `|A||B|`. > > Now suppose I break that up into 2 elements: `A|` followed by `B`. When I > submit the form (a smart grid, in my case), it comes back with a single > element: `A||B`, with the internal representation `|A|||B|`. > > The same thing happens if the 2 elements as `A` followed by `|B`: single > element `A||B`, internally `|A||B|`. > > This looks like a bug to me, but thought I'd check here first. I'm using > v2.16.1 under python2.7 on MacOS 10.12.6 > > - Scott > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
