Username length mismatch causing truncation error in Jmix system entities

Support
#1

Hii all,I am facing an issue related to username length in Jmix.

In my application, the User table allows usernames longer than 50 characters (for example, 55+ characters). Creating such users works fine.

However, when Jmix creates records in core entities like:

  • ResourceRoleEntity
  • ResourcePolicyEntity
  • RowLevelRoleEntity

the fields:

  • createdBy
  • updatedBy
  • deletedBy

seem to have a maximum length of 50 characters.

Problem

If a user has a username longer than 50 characters, and performs any action that creates or updates these entities, I get the following error:

Caused by: org.hsqldb.HsqlException: data exception: string data, right truncation
#2

Hello, Manikandan!

Thank you for reporting the issue! We have a ticket to resolve this problem, see: Remove limitation of 50 symbols for createdBy attribute for all system entities · Issue #3351 · jmix-framework/jmix · GitHub

#3

Hi,

Thanks for the update and for sharing the issue link.

Just to confirm, can I proceed with increasing the column size using a Liquibase changelog on our side? For example, I’m planning to modify the CREATED_BY , UPDATED_BY , and DELETED_BY columns in the SEC_RESOURCE_ROLE table to varchar(255) using a changeSet.

Please let me know if this approach is safe and won’t conflict with future framework updates, or if you recommend waiting for the official fix.

Thanks!

#4

Hi,

Thanks for the update and for sharing the issue link.

Just to confirm, can I proceed with increasing the column size using a Liquibase changelog on our side? For example, I’m planning to modify the CREATED_BY , UPDATED_BY , and DELETED_BY columns in the SEC_RESOURCE_ROLE table to varchar(255) using a changeSet.

Please let me know if this approach is safe and won’t conflict with future framework updates, or if you recommend waiting for the official fix.

Thanks!

#6

Hi,

We will update those fields in the system entities to a length of 255 in Jmix 3.0.

You can try updating them in your project. The same modifyDataType operations should not break the database when you migrate to Jmix 3.0.

#8

Hi,

Thank you for the update.

We will proceed with updating the field lengths to 255 in our project as suggested. Good to know that the same modifyDataType operations will remain compatible with Jmix 3.0 migration.

Appreciate your guidance on this.

Thanks again!