[raster] raster overview -- trying to insert into wrong table (if schema qualify), and not creating rast column

[robe]

I didn't check to see if its the permutation of options we were using, but we ran into two issues with raster overviews.

If we do something like this (basically creating a schema qualified raster table

python raster2pgsql.py -r *.jpg -l 2 -t aerials.boston -s 26986 -k 100x160 -F -I -o bostonaerials_overview.sql

1) It tries to insert into a table called aerials.raster_overviews instead of the one that gets pre-installed in public.

2) Also its not doing an AddRasterColumn call so that the new overview table fails because it has not raster column. Though when I tried this I was doing just

python raster2pgsql.py -r *.jpg -l 2 -t boston -s 26986 -k 100x160 -F -I -o bostonaerials_overview.sql

So not absolutely sure it would fail for the first case.

[robe]

On a related topic I think we are also agreed that we don't really need the -V switch anymore. So the raster_overviews insert should not assume the raster_overviews is in the same schema as the loading raster and also for flexibility just not schema qualify the raster_overviews table

​http://www.postgis.org/pipermail/postgis-devel/2011-February/011793.html

I have also confirmed that the raster2pgsql doesn't seem to do the AddRasterColumn call for overviews or even create a raster column so always requires manual edit or the file to work properly.

[jorgearevalo]

Problem 1 fixed in r7038.

[Bborie Park]

No longer valid as raster_overview is a view now instead of table. Also, AddRasterColumn is deprecated and removed in the near future.