Alex CD ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjJmZDlhZTFj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiZjJmZD... ) HHH-14088 ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiZjJmZD... ) Schema validation fails with same name sequence in different schemas ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiZjJmZD... ) Issue Type: Bug Affects Versions: 5.4.17 Assignee: Unassigned Created: 26/Jun/2020 12:00 PM Priority: Major Reporter: Alex CD ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Using multiple schemas with same name sequences but different parameters. I use a default schema name, but the sequence information extractor retrieves all sequences and database information is initialized with sequences devoid of schema name in the order received from the extractor. So if the result is a sequence from default schema followed by the same sequence from another schema, it will be overwritten with invalid schema information. Extractor uses select * from information_schema.sequences ( https://github.com/hibernate/hibernate-orm/blob/604b594226355dc789586c40f... ) to get all sequences disregarding any default schema configuration. Then, DatabaseInformationImpl.java populates sequenceInformationMap in order received from executing the above sql, removing schema qualifier and overwriting without any check. source ( https://github.com/hibernate/hibernate-orm/blob/604b594226355dc789586c40f... ) ( https://hibernate.atlassian.net/browse/HHH-14088#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14088#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#100130- sha1:d095cd6 )