installing raster gives 1 conflict when running populate_geometry_columns()

[nicklas]

After compiling with raster and installing with rtpostgis.sql I get 1 conflict when running populate_geometry_columns().

The column found but not inserted in geometry_columns is column "extent" in table "raster_columns".

so the result of

select populate_geometry_columns()

in a new installed database with raster is:

probed:1 inserted:0 conflicts:1 deleted:0

/Nicklas

[robe]

I think that error is fine. If you have no rasters in the table populate_geometry_columns doesn't know what type it is since its an empty tables. Its also a heterogenous column (would have different polygons of different srids so not terribly useful to insert with populate_geometry_columns.

I recall Pierre and Jorge were thinking of scrapping it anyway since for later loaded tables is not of much use. (that last part I could be wrong about).

[nicklas]

Ok, I get it.

But is there no way of better communicating what the "conflict" is about.

Would it be possible to pass the name of the "conflicting" table or something like that in populate_geometry_columns function?

Or maybe hardcode away this special case.

I think we are risking a lot of confusion otherwise, just because all you get is a message of "conflict" and no clues.

/Nicklas

[robe]

Good point. I guess in this case hard-coding would be called for since I don't see why we would ever want that table listed in geometry_columns, but I'll wait for Jorge and Pierre to respond. If they plan to get rid of the column anyway then I don't think any action needs to be taken.

[robe]

Nicklas,

I forgot but when Paul was visiting us last week, he seemed pretty wanting to get the typmod support for geometry into PostGIS 2.0. If he wakes up from his campaign slumber before we release PostGIS 2.0, this whole discussion may be moot anyway as this function would be obsolete.

[nicklas]

Both alternatives seems great :-)

[pracine]

I think populate_geometry_columns should ignore (not scan) the raster_columns table even if it contains a geometry column.

[robe]

I'm going to close this as a won't fix. We are going to have to redo populate_geometry_columns for typmod and when we do, there ain't going to a geometry_columns to be populating.