Hi Margot, thanks for the feedback.
5.1.4 introduced a new default strategy used to retrieve JDBC Metadata that requires the the default_schema to be provided. In order to obtain the previous behaviour the hibernate.hbm2ddl.jdbc_metadata_extraction_strategy can be set to 'individually'. I created a new Jira https://hibernate.atlassian.net/browse/HHH-11808 Thanks again. On 7 June 2017 at 17:01, Margot PIVA <margot.p...@smile.fr> wrote: > > > Hello, > > For the need of our project we had to upgrade the version of > Hibernate from 5.1.2.Final to 5.2.10.Final. > We referred to the changelog > to adapt our code and it worked perfectly well except that > Hibernate > couldn't find our schema event though it was declared on the > search_path of our PostgreSQL database > configuration (at user's level). > We observed that this behavior appeared from (and including) the version > 5.1.4.Final, > and we supposed that it came from this bugfix : > https://hibernate.atlassian.net/browse/HHH-11023 > > Finally we found out > that we had to specify the default_schema directly to Hibernate and we > thought > that it would be favourable to point this necessity out. > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
