#5072 BLOC Update.: Activities dont load in 640

[Zarro Boogs per Child]

#5072: Activities dont load in 640
------------------------+---------------------------------------------------
  Reporter:  yani       |       Owner:  tomeu            
      Type:  defect     |      Status:  new              
  Priority:  blocker    |   Milestone:  Update.1         
 Component:  datastore  |     Version:                   
Resolution:             |    Keywords:  Update.1? review?
  Verified:  0          |  
------------------------+---------------------------------------------------

Comment(by marco):

 Replying to [comment:12 tomeu]:
 > Model.apply() looks to me like it syncs from Model to Xapian, isn't it?
 If we are sync'ing from Xapian to Model, then we don't need to call
 apply().

 It matters in this case because our code assumes all custom properties are
 "string" and Xapian has a different opinion. If secore exposes type
 information maybe the right solution is to actually respect it. In any
 case we need to check and resolve the inconsistency immediately, we can't
 let it run until it chokes at some random point.

 > >  * For Ship.2 I'm likely going to recommend to *not* apply the custom
 property patch. Source should not be a string in first place, we can keep
 defining it as "text" in model.py until it's worth to break model
 compatibility. Anyway we should think a bit more about it tomorrow morning
 and make a call in the Journal meeting.
 >
 > Perhaps that's the best thing we can do, but I'm a bit worried of
 setting source as "text", as this will be indexed, reducing performance in
 some unknown measure. 'string' is wrong but 'text' looks definitely worst
 to me.

 I doubt it will have any user visible effects for the source property. Do
 you disagree?

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