Skip to content

Conversation

@XingY
Copy link
Contributor

@XingY XingY commented Feb 6, 2026

Rationale

The refactoring of ConvertUtils usages caused a few test failures:

Related Pull Requests

Changes

  • Skip convert for CalculatedExpressionColumn
  • Format date value used in naming expression based on its time portion

return date.format(value);
else if (value instanceof Date)
return defaultDateTimeFormat.format(value).replace('T', ' '); // replace T with whitespace for human readability
else if (value instanceof Date dateVal)
Copy link
Contributor

Choose a reason for hiding this comment

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

This fix seems like good behavior. Is there also a change we can make to ColumnInfo.getConvert() or getJavaClass() to convert to the more specific type?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

PropertyType.Date.convert already does DateUtil.getDateOnly, if that's what you mean?

Copy link
Contributor

Choose a reason for hiding this comment

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

I looked at this a little, I have a PR that changes that method to return java.sql.Date instead of java.util.Date also PropertyType.DATE_TIME convert to return java.util.Timestamp. Haven't run through tests though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants