# \--validCheckSum not taking

**URL:** <https://forum.liquibase.org/t/validchecksum-not-taking/7698>\
**Category:** General Discussion\
**Created:** [January 17, 2023, 10:59pm UTC](https://forum.liquibase.org/t/validchecksum-not-taking/7698 "2023-01-17T22:59:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmenne](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@mmenne](https://forum.liquibase.org/u/mmenne)\
**Post date:** [January 17, 2023, 10:59pm UTC](https://forum.liquibase.org/t/validchecksum-not-taking/7698/1 "2023-01-17T22:59:00Z")

</div>

Hello,

I have an existing changeset in a SQL formatted changelog. Looks like this:

```auto
--liquibase formatted sql

--changeset my.name:dev-1.0.0 label:dev-v1 context:dev
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;

-- --changeset my.name:qa-1.0.0 label:qa-v1 context:qa
-- --comment: a comment
-- USE ROLE MY_ROLE;
-- USE SCHEMA MY_QA_SCHEMA;
-- CREATE STAGE IF NOT EXISTS my_qa_ext_stage
-- URL = 's3://a-bucket'
-- STORAGE_INTEGRATION = AN_INTEGRATION;

```

I was preparing for future changeset’s and mis-commented them. Now I’m trying to make a change to those so they are seen as actual changesets and get a checksum error as expected:

```auto
schemas/external_stages.sql::dev-1.0.0::my.name was: 8:de3b6d85303c32f2d212c69ae2b601e7 but is now: 8:d6e7640ccc986b9a7c8956e6c61be12a

```

So I take that checksum and add a `--validCheckSum` value but it still gives the same checksum error. Here is my attempt:

```auto
--liquibase formatted sql

--changeset my.name:dev-1.0.0 label:dev-v1 context:dev --validCheckSum: 8:d6e7640ccc986b9a7c8956e6c61be12a
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;

--changeset my.name:qa-1.0.0 label:qa-v1 context:qa
--comment: a comment
-- USE ROLE MY_ROLE;
-- USE SCHEMA MY_QA_SCHEMA;
-- CREATE STAGE IF NOT EXISTS my_qa_ext_stage
-- URL = 's3://a-bucket'
-- STORAGE_INTEGRATION = AN_INTEGRATION;

```

What am I doing wrong?

Note that the change on the 2nd changeset line for qa-1.0.0 and the subsequent comment is removing the leading `-- `.

Running v4.18.

---

<div class="post-metadata">

**Author:** ![mmenne](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@mmenne](https://forum.liquibase.org/u/mmenne)\
**Post date:** [January 17, 2023, 11:21pm UTC](https://forum.liquibase.org/t/validchecksum-not-taking/7698/2 "2023-01-17T23:21:17Z")

</div>

Seems like the extra context isn’t really warranted as any change I make doesn’t seem to use the `--validCheckSum` value I provide or the special `1:any` value. Is this a pro only feature? Is my only recourse to manually delete rows from the `databasechangelog` table?

---

<div class="post-metadata">

**Author:** ![daryldoak](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/daryldoak/32/764_2.png) [@daryldoak](https://forum.liquibase.org/u/daryldoak)\
**Post date:** [January 18, 2023, 2:27pm UTC](https://forum.liquibase.org/t/validchecksum-not-taking/7698/3 "2023-01-18T14:27:18Z")

</div>

Your formatting is incorrect. The – attributes need to be on their own line:

```auto
--changeset my.name:dev-1.0.0 label:dev-v1 context:dev 
--validCheckSum: 8:d6e7640ccc986b9a7c8956e6c61be12a
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;

```