DatabaseError: invalid byte sequence for encoding "UTF8": 0x00

[Muharem Hrnjadovic]

Traceback (most recent call last):
  File "/usr/bin/openquake", line 125, in <module>
    job.run_job(FLAGS.config_file, FLAGS.output_type)
  File "/usr/lib/pymodules/python2.7/openquake/job/__init__.py", line 69, in run_job
    a_job = Job.from_file(job_file, output_type)
  File "/usr/lib/pymodules/python2.7/openquake/job/__init__.py", line 362, in from_file
    job_id = prepare_job(params).id
  File "/usr/lib/pymodules/python2.7/django/db/transaction.py", line 217, in inner
    res = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/openquake/job/__init__.py", line 299, in prepare_job
    oqp.save()
  File "/usr/lib/pymodules/python2.7/django/db/models/base.py", line 460, in save
    self.save_base(using=using, force_insert=force_insert, force_update=force_update)
  File "/usr/lib/pymodules/python2.7/django/db/models/base.py", line 553, in save_base
    result = manager._insert(values, return_id=update_pk, using=using)
  File "/usr/lib/pymodules/python2.7/django/db/models/manager.py", line 195, in _insert
    return insert_query(self.model, values, **kwargs)
  File "/usr/lib/pymodules/python2.7/django/db/models/query.py", line 1436, in insert_query
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/lib/pymodules/python2.7/django/db/models/sql/compiler.py", line 791, in execute_sql
    cursor = super(SQLInsertCompiler, self).execute_sql(None)
  File "/usr/lib/pymodules/python2.7/django/db/models/sql/compiler.py", line 735, in execute_sql
    cursor.execute(sql, params)
  File "/usr/lib/pymodules/python2.7/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute
    return self.cursor.execute(query, args)
django.db.utils.DatabaseError: invalid byte sequence for encoding "UTF8": 0x00

[Muharem Hrnjadovic (al-maisan)]

The following django patch: https://code.djangoproject.com/attachment/ticket/16778/postgis-adapter-2.patch needs to be applied on a pristine ubuntu 11.10 system.

[Lars Butler (lars-butler)]

The best solution right now is to simply patch django 1.3. There is no code we can implement right which will fix this.

[Paul Henshaw (paul-sl-henshaw)]

Just for the record, the other workaround for this problem is to change the postgres configuration file postgresql.conf to set

standard_conforming_strings = off

as described here: https://code.djangoproject.com/ticket/16778

This is the approach we took with previous versions of the engine. I agree with Lars that applying the patch is probably the better solution.