[storages] fix fs_importing side-effect on entity.data
When creating a new File object, if fs_importing is set,
we want entity.data to be the file content instead of the
filepath for the rest of the transaction.
(see test_bfss_fs_importing_transparency) for test implementation
To make this possible, the storage hooks (entity_added / entity_updated)
must return the correct value to set in the entity dict.
""":organization: Logilab:copyright: 2001-2010 LOGILAB S.A. (Paris, FRANCE), license is LGPL v2.:contact: http://www.logilab.fr/ -- mailto:contact@logilab.fr:license: GNU Lesser General Public License, v2.1 - http://www.gnu.org/licenses"""fromcubicweb.devtoolsimportbuildconfig,loadconfigfromcubicweb.devtools.testlibimportRealDBTestdefsetup_module(options):ifoptions.source:configcls=loadconfig(options.source)elifoptions.dbnameisNone:raiseException('either <sourcefile> or <dbname> options are required')else:configcls=buildconfig(options.dbuser,options.dbpassword,options.dbname,options.euser,options.epassword)RealDatabaseTC.configcls=configclsclassRealDatabaseTC(RealDBTest):configcls=None# set by setup_module()deftest_all_primaries(self):forrsetinself.iter_individual_rsets(limit=50):yieldself.view,'primary',rset,rset.req.reset_headers()## startup viewsdeftest_startup_views(self):forvidinself.list_startup_views():req=self.request()yieldself.view,vid,None,reqif__name__=='__main__':fromlogilab.common.testlibimportunittest_mainunittest_main()