debian/watch
author Vladimir Popescu <vladimir.popescu@logilab.fr>
Thu, 04 Apr 2013 11:58:41 +0200
changeset 8926 336e4971dc50
parent 8302 7965f1e9f399
child 10290 6d265ea7d56f
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.
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
8302
7965f1e9f399 [debian] add a watch file
Julien Cristau <julien.cristau@logilab.fr>
parents:
diff changeset
     1
version=3
7965f1e9f399 [debian] add a watch file
Julien Cristau <julien.cristau@logilab.fr>
parents:
diff changeset
     2
http://download.logilab.org/pub/cubicweb cubicweb-(.*)\.tar\.gz