[dataimport] backout 6947201033be (related to #2788402)
(and add a try: except to cache the intended error)
The problem actually comes from the ``MassiveObjectStore``
in the ``dataio`` cube, so it should be corrected there.
Here, we only protect it with a ``RuntimeWarning`` so that
the user can see the problem.
``value`` is set to ``None`` (whence to ``NULL`` from
a database standpoint), so that the data can be nevertheless
inserted in the database. However, only the keys present in
``row`` are actually non-'``NULL``'.
The real solution is to work out the issue in ``MassiveObjectStore``
directly.
The current try/except should only be a temporary hack.
<html><head><!-- dependencies --><scripttype="text/javascript"src="utils.js"></script><scripttype="text/javascript"src="../../data/jquery.js"></script><scriptsrc="../../data/cubicweb.python.js"type="text/javascript"></script><scriptsrc="../../data/cubicweb.js"type="text/javascript"></script><scriptsrc="../../data/cubicweb.compat.js"type="text/javascript"></script><!-- qunit files --><scripttype="text/javascript"src="../../../devtools/data/qunit.js"></script><linkrel="stylesheet"type="text/css"media="all"href="../../../devtools/data/qunit.css"/><!-- test suite --><scriptsrc="cwmock.js"type="text/javascript"></script><scriptsrc="test_utils.js"type="text/javascript"></script></head><body><divid="main"></div><h1id="qunit-header">cw.utils functions tests</h1><h2id="qunit-banner"></h2><olid="qunit-tests"></body></html>