importscript error

[[email protected]…]

Heard the performance of the django-based tool had been improved; I'd stopped using it in the bast because it was much, much too slow for the hardware available. However, after initial import, I get the following:

[email protected]:~/devel/debs/bcfg2/bcfg2-0.9.5pre5/src/lib/Server/Reports$ ./importscript.py 
Traceback (most recent call last):
  File "./importscript.py", line 197, in ?
    newitem.save()
  File "/var/lib/python-support/python2.4/django/db/models/base.py", line 238, in save
    ','.join(placeholders)), db_values)
  File "/var/lib/python-support/python2.4/django/db/backends/util.py", line 12, in execute
    return self.cursor.execute(sql, params)
  File "/usr/lib/python2.4/site-packages/MySQLdb/cursors.py", line 165, in execute
    self._warning_check()
  File "/usr/lib/python2.4/site-packages/MySQLdb/cursors.py", line 80, in _warning_check
    warn(w[-1], self.Warning, 3)
  File "/usr/lib/python2.4/warnings.py", line 61, in warn
    warn_explicit(message, category, filename, lineno, module, registry)
  File "/usr/lib/python2.4/warnings.py", line 96, in warn_explicit
    raise message
_mysql_exceptions.Warning: Incorrect integer value: '' for column 'critical' at row 1

I am using mysql as the backend, and I already ran syncdb.

[desai]

I think that I have this fixed in revision [42a3be9cb383d0dc029a9ec6a8eacaf25cc7b2be] (SVN r3884). I only saw this error intermittently, so can you verify that this is now working for you as well?