web/data/images/ui-bg_highlight-soft_100_eeeeee_1x100.png
author |
Vladimir Popescu <vladimir.popescu@logilab.fr> |
|
Thu, 04 Apr 2013 11:58:41 +0200 (2013-04-04) |
changeset 8926 |
336e4971dc50 |
parent 4547 |
5f957e351b0a
|
permissions |
-rw-r--r-- |
[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.