#1216 closed enhancement (fixed)
[raster] Make raster_columns a view
| Reported by: | pracine | Owned by: | pramsey |
|---|---|---|---|
| Priority: | low | Milestone: | PostGIS 2.0.0 |
| Component: | postgis | Version: | master |
| Keywords: | Cc: | mateusz@… |
Description
What do we need to make raster_column a view?
Isn't there a limitations on the quantity of info typmod can take?
Change History (7)
comment:1 by , 13 years ago
| Cc: | added |
|---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
That's the point. We might want to get rid of some of this info but we need to know what are the constraint first. What is the limit on the quantity of info we can keep? Browsing the doc I see that "this information must be capable of being packed into a single non-negative integer value for storage in the system catalogs". Does this mean we have to fit everything which is not r_table_catalog, r_table_schema, r_table_name and r_column into a 32bit int? This is kind of very limitative…
comment:4 by , 13 years ago
yes that is why I quickly dismissed it for raster. The fact you can have an undefined number of bands kind of screws you already. Maybe in the future they will make it more expansive then you can revisit.
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
this is done already and I think it might be a duplicate ticket too.
comment:6 by , 12 years ago
| Summary: | [raster] Make raster_column a view → [raster] Make raster_columns a view |
|---|
archive yanitor
Yah there is so I don't think we can ever make it a view if we want all that information.