Opened 14 years ago
Closed 13 years ago
#617 closed defect (invalid)
uninstall script get rid of drop cascade
| Reported by: | robe | Owned by: | robe |
|---|---|---|---|
| Priority: | blocker | Milestone: | PostGIS 1.5.4 |
| Component: | build | Version: | 1.5.X |
| Keywords: | Cc: |
Description
Can we please get rid of the drop cascade in the uninstall scripts. I was testing and accidentally installed postgis in the wrong schema. When I went to fix the error by using the uninstall script, I blew out all my geometries.
Needless to say I'm a bit irked.
Change History (8)
comment:1 by , 14 years ago
| Summary: | uninstall scrip → uninstall script get rid of drop cascade |
|---|
comment:2 by , 14 years ago
| Priority: | medium → blocker |
|---|
comment:3 by , 13 years ago
| Milestone: | PostGIS 1.5.3 → PostGIS 2.0.0 |
|---|
comment:4 by , 13 years ago
| Milestone: | PostGIS 2.0.0 → PostGIS 1.5.4 |
|---|
comment:5 by , 13 years ago
| Component: | postgis → build/upgrade/install |
|---|---|
| Owner: | changed from to |
comment:6 by , 13 years ago
Robe: we can't get rid of drop cascade for types due to circular dependencies: type requires input/output functions while output function needs type. Unless you handle to solve the puzzle the best we could do is add a check for the presence of tables requiring the type (and excluded the ones we install ourselves). Doesn't seem like an easy task, anyway.
comment:7 by , 13 years ago
| Owner: | changed from to |
|---|
comment:8 by , 13 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Yeah, you're not really uninstalling if you're keeping your data.
Note:
See TracTickets
for help on using tickets.
Came across someone on IRC who was about to do this. So I'm not the only one who makes this fatal mistake. If we are going to be destroying people's data, I really think we should at least warn them about it. Especially for 2.0.