Opened 10 years ago

Closed 9 years ago

#3183 closed defect (fixed)

Logic to upgrade the address_standardizer extensions

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

Description

Right now you can do

CREATE EXTENSION address_standardizer;
CREATE EXTENSION address_standardizer_data_us;

But you can't do ALTER EXTENSION. This not too critical in 2.2.0 except possibly for upgrading from address_standardizer 1.0 for those folks who actually used the std_address type in their tables (Like Leo), but will be more of an issue in 2.2.1.

I also expect to be updating the address_standardizer_data_us (maybe not at 2.2.0 but at 2.2.1 so being able to add new entries without destroying people's custom ones will become more of an issue.

Change History (5)

comment:1 by robe, 10 years ago

Owner: changed from woobri to robe

comment:2 by robe, 10 years ago

More or less done for data extension at r13725 (since this is the first release of it, dev yoyo upgrade is good enough for now)

comment:3 by robe, 9 years ago

Type: enhancementdefect

comment:4 by robe, 9 years ago

I opted for the lazy simple route and just broke the sql script into two - one containing functions, which are always safe to create or replace and one containing types which can only be installed with new install. The type won't change for a while and hasn't since 1.0 so probably good enough.

committed at r13957

comment:5 by robe, 9 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.