Some PostgreSQL error messages break markup.

What steps will reproduce the problem?
1. Try to open a connection to PostgreSQL where the database was deleted.

What is the expected output? What do you see instead?

A error message should appear, telling what went wrong. Instead a dialog 
"Failed" appears.

1263465896.003036 ERROR __init__.py:246 Datasource.dbconnect failed: 
Traceback (most recent call last):
  File "/storage/devel/cf/default/cf/db/__init__.py", line 235, in dbconnect
    conn = self._open_connection()
  File "/storage/devel/cf/default/cf/db/__init__.py", line 215, in 
_open_connection
    conn = self.backend.get_connection(self.url)
  File "/storage/devel/cf/default/cf/db/backends/__init__.py", line 134, in 
get_connection
    conn = self.dbapi().connect(*args, **kwds)
OperationalError: FATAL:  Datenbank >>XXX<< existiert nicht

/storage/devel/cf/default/cf/ui/dialogs.py:52: GtkWarning: Failed to set 
text from markup due to error parsing markup: Error on line 1 char 112: Odd 
character 'n', expected a '=' after attribute name 'existiert' of element 
'<'
  dlg.format_secondary_markup(long)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by albrecht.andi on 14 Jan 2010 at 10:47

andialbrecht / crunchyfrog

Some PostgreSQL error messages break markup. #85