[postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly

[PostGIS]

#2068: [raster] Make out_db column of raster_columns view behave correctly
-----------------------+----------------------------------------------------
 Reporter:  dustymugs  |       Owner:  dustymugs    
     Type:  defect     |      Status:  assigned     
 Priority:  medium     |   Milestone:  PostGIS 2.0.2
Component:  raster     |     Version:  2.0.x        
 Keywords:             |  
-----------------------+----------------------------------------------------
Changes (by mloskot):

 * cc: mateusz@… (added)


Comment:

 Here is my chat on this problem with dustymags last night, copied from
 http://irclogs.geoapt.com/postgis/%23postgis.2012-10-26.log

 {{{
 00:17:41        mloskot:        dustymugs: here is the story
 00:17:50        mloskot:        1. create table with raster column
 00:18:03        mloskot:        2. Insert images
 00:18:44        mloskot:        3. AddRasterConstraints(..., FALSE, TRUE)
 -- means I say FALSE for out_db constraints
 00:19:05        dustymugs:      ok
 00:19:07        mloskot:        Does it mean, I require the out_db field
 in raster_columns has NULL value?
 00:19:48        mloskot:        or default value (whatever it is)
 00:19:48        dustymugs:      let me jog my memory
 00:20:36        mloskot:        dustymugs: no rush, I'll try to catch you
 tomorrow, it's afte 1am for me, so heading off now
 00:20:44        dustymugs:      OK
 00:21:01        dustymugs:      looking at my main raster db, the out_db
 column is NULL...
 00:21:06        mloskot:        dustymugs: simply, I have an impression
 the constraints could be documented better, but first I have to understand
 it well :)
 00:21:10        mloskot:        right
 00:21:23        dustymugs:      yeah... I really need to refresh my memory
 about this
 00:21:32        mloskot:        but, if the out_db constraint is set to
 TRUE, then we have two options:
 00:21:51        dustymugs:      probably need to check the tickets related
 to this very column
 00:21:57        mloskot:        a) if it's in-db raster, e.g. 3 bands,
 value will be {f,f,f}
 00:22:01        dustymugs:      I think there is something historical...
 00:22:06        mloskot:        b) if out-db ratser, then {t,t,t}
 00:22:24        dustymugs:      your A and B examples are what the ideal
 should be
 00:22:25        mloskot:        so, FALSE means UNKNOWN, thus seems imply
 NULL
 00:23:09        dustymugs:      FALSE in the addrasterconstraint means
 that the function does NOT attempt to add the outdb constraint... so, the
 out_db column would be NULL
 00:23:22        mloskot:        ok, that makes sense
 00:23:27        dustymugs:      BUT!!!!
 00:23:30        mloskot:        ?
 00:23:56        dustymugs:      by the looks of my production database, I
 DO have the outdb constraint on my raster columns
 00:24:05        dustymugs:      AND the out_db column is NULL
 00:24:23        dustymugs:      It should have some {t} or {f}
 combinations
 00:24:35        mloskot:        yup
 00:25:03        dustymugs:      I'm almost certain there is something
 historical reason why I didn't follow through with it
 00:25:16        dustymugs:      I'll need to dig through emails and the
 tickets to see what is up
 00:25:38        dustymugs:      for 2.1, I will make the behavior
 consistent though... heck... new ticket time
 00:25:50        mloskot:        it's not that important, but in case you'd
 have a spare moment to find that, I'd appreciate, no rush though
 00:25:52        mloskot:        cheers
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2068#comment:2>
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.