[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.
/*div.time-holder {
position: relative;
display: none;
z-index: 99;
width: 100px;
}
div.time-holder div.times {
position: absolute;
top: 0;
height: 120px;
overflow: auto;
background: #fff;
border: 1px solid #000;
}
div.time-holder div.times ul {
list-style-type: none;
margin: 0;
padding: 0;
width: 80px;
}
div.time-holder div.times li {
padding: 1px;
}
div.time-holder div.times li.selected {
background: #316AC5;
color: #fff;
}
*/
div.time-picker {
position: absolute;
height: 200px;
width: 5em; /* needed for IE */
overflow: auto;
background: #fff;
border: 1px solid #000;
z-index: 99;
}
div.time-picker-12hours {
width:8em; /* needed for IE */
}
div.time-picker ul {
list-style-type: none;
margin: 0;
padding: 0;
}
div.time-picker li {
background: none;
list-style-type: none;
padding: 1px;
cursor: pointer;
}
div.time-picker li.selected {
background: #316AC5;
color: #fff;
}
input.timepicker {
width: 5em;
}