It does. The problem, however, is that it requires manual intervention
in the changelog.
One could imagine that liquibase would have some information about what
some valid default values are in a table, and when they are extracted,
this should be reflected.
Markus
-Original Message-
From
Hi folks,
I'm at a loss. I have a changelog file that has been working great for
months. Now, suddenly, it's trying to re-create the first table. The
DATABASECHANGELOG table contains a row that identifies that change by ID
and Author, and I have verified that they match what is in the
chang
I found my answer in the time it took for this message to post. The
changelog.xml file was not in the exact same directory as when the
original update was run. I'm curious - why does the directory and
filename matter? Shouldn't the ID be enough?
Thanks,
Dave
David C. Hicks wrote:
> Hi folk
Hi Dave,
I guess the filename matters, because you could have in theory two
different files with the same changeset, but they should be applied in
different contexts. So, the filename is besides id and author another
attribute, which uniquely identifies a particular changeset.
Nevertheless, one w
A good example of duplicate ids/authors is if you use an incrementing
number for your ids. Each changelog would have changeset ids 1,2,3,4
etc. and so they wouldn't be unique across all changelogs. Adding the
filename and path as part of the identifier makes it so you can use that
id scheme (and
I see. I had not considered the possibility of multiple changelogs.
That's a good point, in case.
Renzo - Thanks for the pointer on logicalFilePath. I'll check that out.
Regards -
Dave
Voxland, Nathan wrote:
> A good example of duplicate ids/authors is if you use an incrementing
> number for yo
