#5134 NORM Never A: Better custom properties support

[Zarro Boogs per Child]

#5134: Better custom properties support
------------------------+---------------------------------------------------
  Reporter:  marco      |       Owner:  tomeu         
      Type:  defect     |      Status:  new           
  Priority:  normal     |   Milestone:  Never Assigned
 Component:  datastore  |     Version:                
Resolution:             |    Keywords:                
  Verified:  0          |  
------------------------+---------------------------------------------------

Comment(by tomeu):

 Right now, the DS have some degree of support for setting the data type of
 custom properties like this:
 {{{
 metadata['source:int'] = 1
 }}}

 What worries me is that some activities can do that, and some others could
 do
 {{{
 metadata['source:string'] = 'Wikipedia'
 }}}


 Then, to what type should we cast the result of queries that include those
 values?

 One possibility is to encode the data type in the field name in the index,
 so we would have two source properties: source_int and source_string.

 Another, perhaps safest, is to use always string and let activities
 interpret it as they feel better.

 A related problem is how we allow activities express that a custom
 property should be indexed for fulltext searches.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5134#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system