author | schlatterbeck <schlatterbeck@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Wed, 16 Mar 2011 11:26:50 +0000 (11:26 +0000) | ||
committer | schlatterbeck <schlatterbeck@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Wed, 16 Mar 2011 11:26:50 +0000 (11:26 +0000) | ||
commit | b061d3e9508435b4c9c687743a2c95e385815637 | |
tree | a19b0848196e80fbf66d5fad5dff0d63d7fdd01c | tree | snapshot |
parent | c68ba64226b55817af239e1c5b1fbc316caf6eb6 | commit | diff |
Configuration issue: On some postgresql 8.4 installations (notably on
debian squeeze) the default template database used for database
creation doesn't match the needed character encoding UTF8 -- a new
config option 'template' in the rdbms section now allows specification
of the template. You know you need this option if you get the error
message:
psycopg2.DataError: new encoding (UTF8) is incompatible with the
encoding of the template database (SQL_ASCII)
HINT: Use the same encoding as in the template database, or use
template0 as template.
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4580 57a73879-2fb5-44c3-a270-3262357dd7e2
debian squeeze) the default template database used for database
creation doesn't match the needed character encoding UTF8 -- a new
config option 'template' in the rdbms section now allows specification
of the template. You know you need this option if you get the error
message:
psycopg2.DataError: new encoding (UTF8) is incompatible with the
encoding of the template database (SQL_ASCII)
HINT: Use the same encoding as in the template database, or use
template0 as template.
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4580 57a73879-2fb5-44c3-a270-3262357dd7e2
CHANGES.txt | diff | blob | history | |
roundup/backends/back_postgresql.py | diff | blob | history | |
roundup/configuration.py | diff | blob | history |