[postgis-devel] [PostGIS] #944: typmod support for PostGIS geometry
PostGIS
trac at osgeo.org
Fri May 20 05:04:36 PDT 2011
#944: typmod support for PostGIS geometry
-------------------------+--------------------------------------------------
Reporter: robe | Owner: pramsey
Type: enhancement | Status: new
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis | Version: trunk
Keywords: |
-------------------------+--------------------------------------------------
Comment(by robe):
Okay as I mentioned in hindsight -- the trick to make views appear
correctly in our meta table is probably the same trick I use in other
views for having them register correctly in information_schema etc.
SELECT ST_Transform(geom,4326)::geometry(POINT,4326)
etc.
So I guess a bit of a false alarm there.
Honestly though -- I'm beginning to like my hybrid idea much better now
that I have heard all of your dilbert ideas :)---. In fact I would say my
hybrid is not an ugly duckling at all but quite pretty and is the only
solution thus for that satifies everybody's needs.
Really what is so bad about having a UNION ALL or even an EXCEPT in a
view. I do it all the time and it will work for everyone.
So to clarify -- this is what I propose our geometry_columns look like
{{{
-- just for upgrading --
ALTER TABLE geometry_column RENAME TO geometry_columns_additional;
-- end upgrading --
CREATE VIEW geometry_columns AS
SELECT ...
FROM pg_catalogs blah blah blah
WHERE geometry_typmod_type(a.atttypmod) != 'Geometry'
UNION ALL
SELECT ..
FROM geometry_columns_additional;
}}}
BTW Mark -- I don't care what you say -- I am still vehemently against
screwing around with pg_catalog tables regardless of how much we think we
know about them. All we need is someone coming back yelling at us because
we screwed up their data because they had some strange setup we didn't
account for.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/944#comment:21>
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