[postgis-tickets] [PostGIS] #3260: parse_address function screws up when zip is > 5 characters
PostGIS
trac at osgeo.org
Sun Aug 23 23:35:03 PDT 2015
#3260: parse_address function screws up when zip is > 5 characters
----------------------------------+---------------------------
Reporter: robe | Owner: robe
Type: defect | Status: closed
Priority: medium | Milestone: PostGIS 2.3.0
Component: pagc_address_parser | Version: trunk
Resolution: fixed | Keywords:
----------------------------------+---------------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
Comment:
Fixed at r13992
Hopefully I didn't break anything fixing this. The only regress that
failed (was one that had the issue I raised and now it shows the right
answer). All other tests still work as expected.
and this now returns right answer:
{{{
SELECT (each(hstore(a))).* FROM parse_address('212 3rd Ave N, MINNEAPOLIS,
MN 553404') As a;
key | value
----------+---------------
num | 212
zip | 55340
city | MINNEAPOLIS
state | MN
street | 3rd Ave N
country | US
street2 |
zipplus | 4
address1 | 212 3rd Ave N
(9 rows)
}}}
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3260#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list