[postgis-devel] [PostGIS] #1343: raster Upgrade script doesn't work because of new type

[PostGIS]

#1343: raster Upgrade script doesn't work because of new type
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  pracine      
     Type:  defect          |      Status:  new          
 Priority:  high            |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------
 I see someone created a bandmetadata type.  Can we get rid of it?
 and instead use out parameters.   The band metadata function that uses it
 already has OUT parameters so actually may cause a problem if those get
 out of synch. Though maybe this isn't possible since the first is exposed
 via a C function.

 I also don't see the point of having the C function use a variadic int.
 Why can't it just atake an array of band numbers so it's consistent with
 ST_Band?

 As a general rule, we should avoid creating types unless they are used a
 lot or are complex objects such as raster.

 The problem with types is that they are difficult to upgrade since
 PostgreSQL has no CREATE IF NOT EXISTS yet for types and even then it
 would be impossilbe to change them.  We could create functions to check
 the system catalogs and create them if they don't exist etc, but that gets
 messy.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1343>
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.