Hello all,
The usecase/problem may sound familiar to some of you:
*You have an application that talks to an underlying database. The
underlying database is being managed by another person, service, or
company (and, for the scenario described, worst-case is a database
maintained by a competito
"*You have an application that talks to an underlying database. The
underlying database is being managed by another person, service, or
company (and, for the scenario described, worst-case is a database
maintained by a competitor that you are rewriting the application to
replace, but maintain
rge.net
Subject: Re: [Liquibase-user] Heartbeat concept
"*You have an application that talks to an underlying database. The
underlying database is being managed by another person, service, or
company (and, for the scenario described, worst-case is a database
maintained by a competitor that y
