Opened 12 years ago
Closed 12 years ago
#18710 closed Uncategorized (invalid)
new encoding (UTF8) is incompatible with the encoding of the template database
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
createdb my_prod -E UTF8 -T template0
createdb: database creation failed: ERROR: 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.
createdb: database creation failed: ERROR: 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.
=====
use the following instead:
createdb template_postgis -E UTF8 -T template0
Note:
See TracTickets
for help on using tickets.
This is not related to Django at all. You have to fix the encoding of at least one of your templates. If you have no databases yet, it's simpler to drop and recreate the cluster with the proper encoding (see http://jacobian.org/writing/pg-encoding-ubuntu/). There are other methods to drop and recreate the templates only, Google is your friend.