# Message regarding an empty result set for databasechangeloglock (in 3.0.2 but not in 3.0.0)

**URL:** <https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock-in-3-0-2-but-not-in-3-0-0/2337>\
**Category:** General Discussion\
**Created:** [July 30, 2013, 10:10am UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock-in-3-0-2-but-not-in-3-0-0/2337 "2013-07-30T10:10:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mallim](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@mallim](https://forum.liquibase.org/u/mallim)\
**Post date:** [July 30, 2013, 10:10am UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock-in-3-0-2-but-not-in-3-0-0/2337/1 "2013-07-30T10:10:00Z")

</div>

Scenario With No Such Error:

- Run with liquibase.integration.spring.SpringLiquibase
- Executed against mysql database

Any reason why the older version is more stable than the newer one?

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [July 30, 2013, 10:10am UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock-in-3-0-2-but-not-in-3-0-0/2337/2 "2013-07-30T10:10:00Z")

</div>

I created&nbsp;[https://liquibase.jira.com/browse/CORE-1414](https://liquibase.jira.com/browse/CORE-1414)&nbsp;to track the issue. I haven’t gotten a chance to see what caused the regression yet.

Nathan
