Better Handling of Constraints/Indices after Table Rename #56
Description
Current implementation will not allow foreign keys to be dropped or renamed via ardb after a table rename. The drop_foreign_key will attempt to drop 'fk_[NEW TABLE NAME]...', thus orphaning the foreign_key from ardb.
In addition the primary key, much like the indices and foreign keys, is not updated to match the new table name on rename. Mechanisms to either rename this constraint or have ardb assist in those renames during the table rename may be needed.