debian/cubicweb-ctl.install.in
author Vladimir Popescu <vladimir.popescu@logilab.fr>
Thu, 04 Apr 2013 11:58:41 +0200
changeset 8926 336e4971dc50
parent 858 e6ae125d5903
child 9208 7ae95f48e2f0
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.

debian/tmp/usr/bin/cubicweb-ctl usr/bin/
debian/tmp/usr/lib/PY_VERSION/site-packages/cubicweb/cwctl.py usr/lib/PY_VERSION/site-packages/cubicweb
debian/cubicweb-ctl.bash_completion etc/bash_completion.d/cubicweb-ctl