Opened 17 years ago
Closed 17 years ago
#7731 closed (duplicate)
PostgreSQL requires DROP ... CASCADE when reseting app on which other apps depend
| Reported by: | wiz | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | yandex-sprint | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
psql output (sql&error dump): http://dumpz.org/1631/
Test project: http://narod.ru/disk/1425336000/reset-depended.tbz.html
I dumped data from app and tried to reset it, got failure message complaining about dependent objects with a hint for CASCADE. But there's no way to ask reset code to [automatically] produce a SQL with CASCADE code.
Reset code should temporarily disable (drop?) constraint for that dependent application and reenable(recreate) it afterwards.
Change History (2)
comment:1 by , 17 years ago
| Keywords: | yandex-sprint added |
|---|
comment:2 by , 17 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This is essentially a duplicate of #2493. reset (and sqlreset) are known to have some pretty major problems caused by constraints, and these problems aren't Postgres specific. Fixing these problems is not a trivial operation, either.