Hi gang,
Over the last many months, we (the team and I) have been learning a lot
about a lot of things. One of the things that we somewhat recently came
to realize is that our changelog.xml is out of control. So, I'm trying
to "refactor" it. I'm loosely following the recommended architecture
I'm just learning to use Liquibase and I also thought about the same. I
would also like to know why this is done the way it is. Doesn't it hinder
future refactorings of the changelog.xml? A couple of questions that come to
mind
-Could the filepath being stored in the changelog table be of the pare
fact that your changelog is large and unwieldy should not matter.
Nathan
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hicks.org]
Sent: Friday, April 10, 2009 2:56 PM
To: Liquibase Users
Subject: [Liquibase-user] changelog refactoring - file path ?
Hi gang,
Over the last many
, 2009 12:21 AM
To: liquibase-user@lists.sourceforge.net
Subject: Re: [Liquibase-user] changelog refactoring - file path ?
I'm just learning to use Liquibase and I also thought about the same. I
would also like to know why this is done the way it is. Doesn't it
hinder future refactori
-user@lists.sourceforge.net
*Subject:* Re: [Liquibase-user] changelog refactoring - file path ?
I'm just learning to use Liquibase and I also thought about the same.
I would also like to know why this is done the way it is. Doesn't it
hinder future refactorings of the changelog.xml? A
