Opened 12 years ago
Closed 9 years ago
#2029 closed defect (invalid)
PostgreSQL geometric to PostGIS type casts missing in extension upgrade script
| Reported by: | robe | Owned by: | pramsey |
|---|---|---|---|
| Priority: | high | Milestone: | PostGIS 2.2.0 |
| Component: | build | Version: | master |
| Keywords: | Cc: |
Description
To my horror, when upgrading from unpackaged, I discovered my free wheeling PostGIS database was missing the new path, lsegment, point etc. casts introduced in:
and therefore could not be wrapped up in neat little extension package.
Have issues with raster too still with unionarg order of operation, seems aggregate is being created before my typedef can kick in or dering but that's in another ticket already.
Change History (6)
comment:1 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Summary: | PostgreSQL geometric to PostGIS type casts missing in upgrade script → PostgreSQL geometric to PostGIS type casts missing in extension upgrade script |
comment:2 by , 11 years ago
| Milestone: | PostGIS 2.1.0 → PostGIS 2.2.0 |
|---|
comment:3 by , 11 years ago
This might have been fixed with strk's recent changes to upgrade generator script. I need to recheck this.
comment:4 by , 10 years ago
| Priority: | blocker → medium |
|---|
comment:5 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Priority: | medium → high |
comment:6 by , 9 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I'm seeing these casts in upgrade scripts, so I think this ticket is now invalid.
Note:
See TracTickets
for help on using tickets.
I was wrong this is only an extension issue because I'm explicitly removing create type cast etc. statements on the postgis side. Forget why I'm doing that. The 20_21 script does have the casts as it should and the 21_minor I don't think does which is also correct.