Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjM0NDhlOTZj... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) HHH-16590 ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) Schema update: PostgreSQL byte array does not accept length as parameter ( https://hibernate.atlassian.net/browse/HHH-16590?atlOrigin=eyJpIjoiNjM0ND... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 11/May/2023 08:43 AM Priority: Minor Reporter: Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In PostgreSQL byte array column (bytea) does not have length parameter. When schema is automatically generaed, it will be correctly generated as bytea. However, during schema update length value from column metadata will be compared with either default value or value from @Column annotation (if present). This will, most likely rhan not, cause alter SQL command to be executed. Data type in this generated command will be exactly the same as one use for table creation. In most cases this will have no effect (except waste of time if PostgreSQL is not “smart” enough to ignore column data type change) but in some situations can cause problems. For example when column is used in view definition. ( https://hibernate.atlassian.net/browse/HHH-16590#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16590#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:84d3b45 )