I see your ticket. The more I think about this, the more I think I would like some more justification for this.
list:boolean? What does it mean? How is this not the same as an integer number? list:double? This makes more sense to me but what kind of data are you going to store in there? Isn't it better to pickle a list or dict? To me list:string and list:int make sense because they can be represented as |a|b|c| and they can be searched |b| in |a|b|c| but list:boolean and list:double bout not be searchable so why not just pickle or json the data? Massimo On Sunday, 30 September 2012 09:14:13 UTC-5, Massimo Di Pierro wrote: > > OK. Open a ticket about this. > > On Sunday, 30 September 2012 08:53:38 UTC-5, VP wrote: >> >> I can't believe noone else has asked for this. I think list:double, >> list:boolean would be naturally desirable. >> >> Now I'm using list:string, but I'll have to convert them to double every >> time. >> >> >> >> >> On Saturday, September 29, 2012 10:34:24 PM UTC-5, Massimo Di Pierro >> wrote: >>> >>> Nobody asked for it. It will still be stores as string so I am not sure >>> what you gain by it that cannot be achieved by a list:string and a >>> IS_LIST_OF(IS_FLOAT_IN_RANGE(...)) validator. >>> >>> On Saturday, 29 September 2012 20:36:36 UTC-5, VP wrote: >>>> >>>> I'm wondering why we can't have list:double as a field type? It seems >>>> a natural thing to have. >>>> >>>> Thanks. >>>> >>> --

