# Upgrade from 4.8 to 4.27 filename issue

**URL:** https://forum.liquibase.org/t/upgrade-from-4-8-to-4-27-filename-issue/10001
**Category:** Uncategorized
**Created:** [December 5, 2024, 6:15am UTC](https://forum.liquibase.org/t/upgrade-from-4-8-to-4-27-filename-issue/10001 "2024-12-05T06:15:30Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sonia](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@sonia](https://forum.liquibase.org/u/sonia)
#### Post date: [December 5, 2024, 6:15am UTC](https://forum.liquibase.org/t/upgrade-from-4-8-to-4-27-filename-issue/10001/1 "2024-12-05T06:15:30Z")

</div>

We have upgraded liquibase v4.8 to v4.27

With v4.8, The filename column in databasechangelog table had values like \*\*/\*\*db/changelog/procs/changelog.yaml

But with v4.27, the filenames are now db/changelog/procs/changelog.yaml

When we run liquibase update,

UPDATE DATABASECHANGELOG SET COMMENTS = ‘’, CONTEXTS = NULL, DATEEXECUTED = GETDATE(), DEPLOYMENT\_ID = ‘1234’, EXECTYPE = ‘RERAN’, LABELS = NULL, MD5SUM = ‘9:2232’, ORDEREXECUTED = 1825 WHERE ID = ‘procs\_1’ AND AUTHOR = ‘a’ AND FILENAME = **‘db/changelog/procs/changelog.yaml’**

For the procs which are marked as runAlways= true, the DATABASECHANGELOG filename is  
/db/changelog/procs/changelog.yaml and the above query doesnt update the DATABASECHANGELOG as the filename in the where condition doesnt match.

Is there any support provided for this issue by liquibase?

---

<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: [December 5, 2024, 2:25pm UTC](https://forum.liquibase.org/t/upgrade-from-4-8-to-4-27-filename-issue/10001/2 "2024-12-05T14:25:19Z")

</div>

There are times where logic to reference filename are modified in the Liquibase code. I seem to recall a change in a recent version that removed the asterisks to simplify the path.

In these cases you would need to manually update the rows in your databasechangelog table to match the new functionality.

I have had to do this a few times over the years. One other time was when updating from 3.x to 4.x, which was a major change to filename references.