[postgis-devel] [PostGIS] #648: ST_Summary starts and ends with a newline
PostGIS
trac at osgeo.org
Sun Oct 24 18:21:58 PDT 2010
#648: ST_Summary starts and ends with a newline
---------------------+------------------------------------------------------
Reporter: mwtoews | Owner: pramsey
Type: defect | Status: new
Priority: low | Milestone: PostGIS 2.0.0
Component: postgis | Version: 1.5.X
Keywords: |
---------------------+------------------------------------------------------
Pick your favourite geometry, pass it to ST_Summary and it will both begin
''and'' end with {{{\n}}} newline characters.
{{{
#!sql
select st_summary(geometry), regexp_replace(st_summary(geometry), E'\\n',
E'\\\\n', 'g')
from (
select 'SRID=4326;POINT EMPTY'::geometry
union all select 'MULTIPOLYGON(((0 0 0, 0 1 1, 1 0 2, 0 0 0)), ((10 10
2, 12 10 4, 12 12 3, 10 10 2)))'::geometry
union all select 'SRID=4326;LINESTRING(0 0 0 0, 1 1 1 1)'::geometry) as
foo;
}}}
If you use pgAdminIII, you incorrectly see blank lines from ST_Summary,
unless you expand the row heights from the default to revel the
multitiline output where text begins on the second line.
The output from multiline PostgreSQL functions (e.g., {{{select
table_to_xml('geometry_columns', true, true, 'foo');}}}) does not have
this behaviour. Newlines should only appear within the text body, and not
on the ends.
--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/648>
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-devel
mailing list