(no subject)
|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
 |
(no subject)
by Alex Soto
::
Rate this Message:
|
|
|
Checksum Validation Error
by Alex Soto
::
Rate this Message:
|
|
|
Re: Checksum Validation Error
by Voxland, Nathan
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
The error message is telling you that it is the changes with an
id of 1 or 2 and author of alex.soto in the add_ip_country_tables.xml
changelog. Setting the md5sum in databasechangelog to null should fix the
problem. Is there a databasechangelog table in a different schema/catalog than
dbo that it is reading from? Is there a duplicate id/author combo of
1/alex.soto or 2/alex.soto in the add_ip_counry_tables.xml file (there should
be a separate validation check for that, but just to make sure there isn’t a
problem with that)? Nathan From:
liquibase-user-bounces@...
[mailto:liquibase-user-bounces@...] On Behalf Of Alex
Soto Hello, I
just migrated to 1.7 and now I get checksum errors on old change logs. I
happens for all my old refactorings. The
error message is not very clear on what is wrong: liquibase.exception.ValidationFailedException:
Validation Failed:
2 change sets check sum
add_ip_country_tables.xml :: 1 :: alex.soto
:: (MD5Sum: 4ca879bcd2d221601a107beb708493bc)
add_ip_country_tables.xml :: 2 :: alex.soto
:: (MD5Sum: b6a42e63e7ccc677fcb4c845f61271f4) I
have already set all checksums to null in the database using this
statement: UPDATE
dbo.DATABASECHANGELOG
SET
md5sum
= null What
else do I need to do? Thanks, Alex
Soto - Amicus
Plato, sed magis amica veritas. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Liquibase-user mailing list Liquibase-user@... https://lists.sourceforge.net/lists/listinfo/liquibase-user |
|
|
Re: Checksum Validation Error
by Alex Soto
::
Rate this Message:
|
|
|
Re: Checksum Validation Error
by Voxland, Nathan
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
That does seem strange, I’ll have to investigate. At least you
found a workaround for the issue. An additional option would be to use the new
<validCheckSum> tag on the changeSet to list the new md5sum. Nathan From:
liquibase-user-bounces@...
[mailto:liquibase-user-bounces@...] On Behalf Of Alex
Soto Thank you Nathan I think there may be a bug because when I change the
checksum with the value I get from the message, the error goes away. For example: UPDATE
dbo.DATABASECHANGELOG
SET
md5sum = '98cbddfd97c3a43eb59a996c5118f14e' where filename='fix_orphan_invoice_items.xml' and id='10' and author='alex.soto' Causes the error to disappear. UPDATE dbo.DATABASECHANGELOG SET md5sum = null where filename='fix_orphan_invoice_items.xml' and id='10' and author='alex.soto' Error comes back. So this tells me that the table and row I'm updating is the
same table and row Liquibase is reading from. On Jul 3, 2008, at 1:50 PM, Voxland, Nathan wrote:
The
error message is telling you that it is the changes with an id of 1 or 2 and
author of alex.soto in the add_ip_country_tables.xml changelog. Setting
the md5sum in databasechangelog to null should fix the problem. Is there
a databasechangelog table in a different schema/catalog than dbo that it is
reading from? Is there a duplicate id/author combo of 1/alex.soto or 2/alex.soto
in the add_ip_counry_tables.xml file (there should be a separate validation
check for that, but just to make sure there isn’t a problem with that)? Nathan From:
liquibase-user-bounces@... [liquibase-user-bounces@...]
On Behalf Of Alex Soto Hello, I just migrated to
1.7 and now I get checksum errors on old change logs. I happens for all
my old refactorings. The error message
is not very clear on what is wrong: liquibase.exception.ValidationFailedException:
Validation Failed: 2
change sets check sum
add_ip_country_tables.xml :: 1 :: alex.soto
:: (MD5Sum: 4ca879bcd2d221601a107beb708493bc)
add_ip_country_tables.xml :: 2 :: alex.soto
:: (MD5Sum: b6a42e63e7ccc677fcb4c845f61271f4) I have already set
all checksums to null in the database using this statement:
UPDATE
dbo.DATABASECHANGELOG
SET
md5sum = null What else do I
need to do? Thanks, Alex Soto - Amicus Plato, sed
magis amica veritas. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE
NOW! Studies have shown that voting for your favorite open source
project, along with a healthy diet, reduces your potential for
chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08_______________________________________________ Liquibase-user mailing list ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Liquibase-user mailing list Liquibase-user@... https://lists.sourceforge.net/lists/listinfo/liquibase-user |
|
|
Re: Checksum Validation Error
by Alex Soto
::
Rate this Message:
|
|
|
Re: Checksum Validation Error
by Voxland, Nathan
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Are many running into a problem? I don’t remember anything in
the 1.7 changes that should generate a difference in md5sums, or the logic for
checking the databasechangelog table. Was it 1.6 you were running before, or an earlier version? Were
there any other differences in how you ran liquibase (JVM change, XML reformat,
OS difference, commandline/ant/maven change? Etc. )? From:
liquibase-user-bounces@...
[mailto:liquibase-user-bounces@...] On Behalf Of Alex
Soto Just you know it, the error also happens for the
"changelogSync" command (as well as update). I have over 100 change sets. I'm updating one by one
with the new checksum. Thanks again, On Jul 3, 2008, at 2:38 PM, Voxland, Nathan wrote:
That
does seem strange, I’ll have to investigate. At least you found a
workaround for the issue. An additional option would be to use the new
<validCheckSum> tag on the changeSet to list the new md5sum. Nathan From:
liquibase-user-bounces@... [liquibase-user-bounces@...]
On Behalf Of Alex Soto Thank
you Nathan I
think there may be a bug because when I change the checksum with the value I
get from the message, the error goes away. For
example:
UPDATE
dbo.DATABASECHANGELOG
SET
md5sum = '98cbddfd97c3a43eb59a996c5118f14e'
|
