[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.

     1

[MESSAGES CONTROL]

     2

disable-msg = C0301

     3

     4

[VARIABLES]

     5

# Enable / disable this checker

     6

enable-variables = yes

     7

additional-builtins = _, display_name

     8

     9

[BASIC]

    10

required-attributes=

    11

attr-rgx = (w|[a-z_][a-z0-9_]{2,30})

    12

variable-rgx = (w|[a-z_][a-z0-9_]{2,30})$

    13

argument-rgx = (w|[a-z_][a-z0-9_]{2,30})$

    14

    15

[TYPECHECK]

    16

generated-members=debug,info,notice,warning,error,critical,exception