Subject | Ghost dependencies |
---|---|
Author | Dan Fisher |
Post date | 2008-11-27T16:07:12Z |
FB 2.0.1 on XP/Win2003.
Hi all, I'm getting a strange problem with dependencies that won't go
away until a db has been backed-up and restored.
When I run a bunch of scripts (run as part of an upgrade process) I
need to drop a table. One script drops all its dependencies and then
commits. The next just drops the table, but this invariably errors
with between 2 and 5 objects reported as being dependent on the table.
The only way to procede is to back-up, restore, and carry on from the
table-dropping script. Then all is well. I'm could start deleting
rows from RDB$Dependencies to try and get around this problem, but I'd
rather find out what the real problem is.
Anyone got any ideas?
Dan
Hi all, I'm getting a strange problem with dependencies that won't go
away until a db has been backed-up and restored.
When I run a bunch of scripts (run as part of an upgrade process) I
need to drop a table. One script drops all its dependencies and then
commits. The next just drops the table, but this invariably errors
with between 2 and 5 objects reported as being dependent on the table.
The only way to procede is to back-up, restore, and carry on from the
table-dropping script. Then all is well. I'm could start deleting
rows from RDB$Dependencies to try and get around this problem, but I'd
rather find out what the real problem is.
Anyone got any ideas?
Dan