#7934 NORM 8.2.0 (: "Read" expects datastore.write(self._jobject, transfer_ownership=True) to leave valid file_path

[Zarro Boogs per Child]

#7934: "Read" expects datastore.write(self._jobject, transfer_ownership=True) to
leave valid file_path
-----------------------------+----------------------------------------------
   Reporter:  homunq         |       Owner:  morgs               
       Type:  defect         |      Status:  closed              
   Priority:  normal         |   Milestone:  8.2.0 (was Update.2)
  Component:  read-activity  |     Version:  not specified       
 Resolution:  wontfix        |    Keywords:                      
Next_action:  design         |    Verified:  0                   
  Blockedby:                 |    Blocking:                      
-----------------------------+----------------------------------------------
Changes (by morgs):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 Replying to [ticket:7934 homunq]:
 > When sharing, the Read instance joining gets the file and puts it into
 the datastore with transfer_ownership=True. This moves the file, yet does
 not change the file_path of the jobject (only the uid is changed), so Read
 loses track of the file. How should Read find the file again after this
 call?

 This is by design. Within the datastore, transfer_ownership maps to
 can_move. Hence, it moves. Read shouldn't expect anything else.

 I'm solving the problem you encountered in Read itself by hard linking the
 file to keep it around.

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