NPE when building diff -> Catalog.toString() is null about liquibase-hibernate HOT 3 CLOSED

Some precisions:

1. I'm using ant task through maven to run my diff
2. Im' comparing Hibernate with Mysql schema
3. If I set referenceDefaultCatalogName="" in my ant task, it works

from liquibase-hibernate.

Hi,

i am currently experiencing the same on LB 3.0.8... That's unfortunate.

https://liquibase.jira.com/browse/CORE-1685

No offense guys, but there seems to be a pattern. During ~2 days spent exploring Liquibase itself and Liquibase Hibernate Extension I have experienced sky high level of general fragility, traps, gotchas and NPEs in whole variety of situations it is no fun and has no competion. And I have just scratched the surface with trivial text book cases. If this software was written in native unmanaged code, all those NPEs would be represented by hard crashes, violations or segfaults. There's no excuse, NPEs are NPEs. On the other hand LB can't be as that bad if companies like Atlassian are using it in their products, right? Perhaps one just have to closely follow a specific (top secret) narrow path to stay safe, but once you deviate from it be prepared for adrenaline experience and headaches. Still, such teething problems are not expected from a software that's been around for ~7 years. Way to unimpress a newcomer.

https://liquibase.jira.com/browse/CORE-1641?jql=text%20~%20%22nullpointerexception%22%20or%20text%20~%20%22NPE%22

Regards,
Tomas

from liquibase-hibernate.

This has been fixed with later liquibase versions.

Sorry for any problems you were having. Improving testing is one of my highest priorities at the moment, especially for the extensions outside the main codebase like the hibernate extension.

from liquibase-hibernate.