Opened 11 years ago

Closed 10 years ago

#2814 closed defect (fixed)

address_standardizer does not install with all encodings of database

Reported by: robe Owned by: woobri
Priority: high Milestone: PostGIS 2.2.0
Component: pagc_address_parser Version: master
Keywords: Cc:

Description 

CREATE DATABASE test3
  WITH OWNER = postgres
       ENCODING = 'WIN1252'
       TABLESPACE = pg_default TEMPLATE=template0;

If I try to install the address_standardizer on a database with encoding WIN1252, I get error 

default conversion function for encoding 'LATIN1' to 'WIN1252' does not exist

If we can't fix this, we probably need to make a note of it in the docs that people use UTF8 for their database encoding.

Change History (1)

comment:1 by robe, 10 years ago

Resolution: → fixed
Status: new → closed

Problem seems to be in the .control file. The line had

encoding = 'LATIN1'

I read here ​http://www.postgresql.org/docs/current/static/extend-extensions.html seems that's only useful if your script file has non-ASCII characters. This may be the case when we get to dataset extensions but doesn't seem relevant for the actual address_standardizer extension itself.

Committed at r12820

Note: See TracTickets for help on using tickets.