OK, I got it. On web2py level it is now a list of strings all the way.
That makes sense of course as it simplifies the usage. Internally its
'|' separated concatenation on RDBMS and list property on GAE, which
also makes sense.
What confused me was the fact that if you use simple "string" instead
On relational database with type="list:string" the internal
representation is the same as before '|xxx|yyy|zzz|' but it is no
longer exposed to the user. The user inserts a list a string and
extract a list of strings.
On GAE things have changed. At the web2py level the user still inserts
a list of
As far as I can see, when "list:string" is being used the effect is
very similar (I'm testing this on GAE). Again a list like
representation is used (this time using unicode):
[u'xxx',u'yyy',u'zzz'], not the old '|' separated strings. Does it
mean that now this is the new way of representing a list
I checked and it works for me (insert is correct) but retrieval is not
correct because
db.define_table("aaa", db.Field("bbb"), migrate=False)
should be
db.define_table("aaa", db.Field("bbb","list:string"), migrate=False)
You should be able to change this and data in db should be file.
With
4 matches
Mail list logo
