Thomas Mortagne created HIBERNATE-165: ----------------------------------------- Summary: SequenceInformationExtractor does not take into account the schema indicate in ExtractionContext on PostreSQL Key: HIBERNATE-165 URL: https://issues.jboss.org/browse/HIBERNATE-165 Project: Hibernate Integration Issue Type: Bug Environment: PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions) Reporter: Thomas Mortagne Assignee: Steve Ebersole When asking for the sequences located on schema "toto" when end up with those stored in the schema "public". Among other things the consequence is that the SchemaMigrator (my actual use case) create the sequences only on one schema (because when creating others the sequence "already exist"). It's also because the schema migrator totally ignore the schema name from the SequenceInformation but it does not make much sense to me that it end up with sequences from other schemas when asking for them in the first place anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)