Select to view content in your preferred language

More robust object deletions in Catalog (EGDB)

268
0
07-13-2022 03:25 PM
Status: Open
Labels (1)
Bud
by
Esteemed Contributor

When deleting objects from Catalog (tables, FC, and especially views) in an enterprise GDB, we never really know if deleting the object worked or not. We delete the object, and it certainly looks like it was deleted, but then when we refresh the connection, the object reappears (it wasn't actually deleted).

Could deleting objects in Catalog be improved? I.e., could Catalog do a better job of deleting an object. And if it wasn't successfully deleted (either the underlying db object or the records in the system tables), make it clearer that the operation failed — so that we know that we need to go back and refresh the connection and troubleshoot the issue.