Removing Deprecated Objects from Database and Source Tree

General Discussion
1

Greetings everyone, I have a general question about how to handle deprecated objects.

We’re using liquibase (community and not the SQL-CL version) with an Oracle database. We’re using formatted sql change sets with a single XML controller file that sits at the top of our directory structure and does an includeAll on each of the following directories in the desired order.

.
├── context
├── db_link
├── dml
├── documentation
│   └── images
├── foreign_keys
├── function
├── grant
├── integration
├── job
├── operation_scripts
│   └── certs
│       ├── fin
│       ├── ti-dev.drw
│       ├── ti.drw
│       └── wildcard
├── package
├── post_install
├── pre_install
├── privilege
├── procedure
├── python_utils
├── rest_module
├── role
├── seed_data
│   └── script_gen_util
├── sequence
├── synonym
├── table
├── temp_table
├── trigger
├── type

This is working great, but now I have a conundrum.

If an object (say, a package) becomes deprecated and we want to drop it, I’m wondering how to deal with this. Ideally we’d want the package to be removed from the database and for we’d like to be able to remove the package spec and body files from the source tree as well.

The same would hold true for a table, view, etc.

What’s the most common way of dealing with this?

My initial instinct would be to:

  1. Remove the script from its place in the tree
  2. create (or add an entry to) a post install script that drops the object(s) being deprecated - with the appropriate pre-condition checks

However, I feel that this would leave some “hanging chads” in the DATABASECHANGELOG table. Is that something I should really worry about?

Thanks in advance.

Doug

2

Here is a documentation page that might help, but it doesn’t address deleting from databasechangelog table.

I’m not sure I would worry about those rows in databasechangelog table, but you could just delete them.

3

Thanks … I’ll have a look at this.

I don’t think its a big deal to leave the rows in the DATABASECHANGELOG, but if there was a natural way to “clean that up” I didn’t want to miss it.

1 Like