Opened 11 years ago
Last modified 7 years ago
#2355 new defect
Upgrade to change box cast to assignment
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | low | Milestone: | PostGIS Fund Me |
Component: | postgis | Version: | master |
Keywords: | Cc: |
Description
This is related to #2262 That takes care of new installs, but doesn't fix existing. I'm not sure how to change our machinery to drop and recreate a cast. As I recall I was able to drop the PostgreSQL box cast without any consequences so we could just do a
DROP CAST .. IF EXISTS; CREATE CAST ;
I don't know how else to do it except my favorite DO call.
I suppose we could just always drop and recreate it too.
Anyway this isn't too big of a deal and doesn't need to be fixed for 2.1.0 (can wait for a micro). Only Bruce noticed the issue.
Change History (4)
comment:1 by , 11 years ago
Milestone: | PostGIS 2.1.0 → PostGIS 2.2.0 |
---|
comment:2 by , 10 years ago
Owner: | changed from | to
---|
comment:3 by , 9 years ago
Milestone: | PostGIS 2.2.0 → PostGIS Future |
---|
comment:4 by , 7 years ago
Milestone: | PostGIS Future → PostGIS Fund Me |
---|
Note:
See TracTickets
for help on using tickets.
Milestone renamed