Skip to content

TRUNK-000: Add null safety check in MySQLBooleanType #6005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Kanishka680 wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −0
Open

TRUNK-000: Add null safety check in MySQLBooleanType #6005

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions api/src/main/java/liquibase/ext/datatype/core/MySQLBooleanType.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,9 @@ public class MySQLBooleanType extends BooleanType {

@Override
public DatabaseDataType toDatabaseDataType(Database database) {
if (database == null) {
Copy link
Copy Markdown

@ashuverma25 ashuverma25 Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementing null safety guards in the database layer is a fundamental best practice for preventing unpredictable NullPointerExceptions. The logic here is concise and matches the core module's patterns.

return super.toDatabaseDataType(database);
}
if (database instanceof MySQLDatabase) {
DatabaseDataType result = new DatabaseDataType("TINYINT", 1);

Expand Down