Oops, to everyone this time :) Hibernate automatically determines the Dialect to use based on JDBC metadata *if* a Dialect is not explicitly set. In fact letting it auto detect is the recommended behavior, just setting Dialect explicitly when using a custom Dialect for some reason. There is also a way to affect the auto resolution (for integrators).
On Mon, Feb 3, 2014 at 10:06 AM, Bill Burke <bbu...@redhat.com> wrote: > Hey, > > My Hibernate knowledge is really dated, but, within a Wildfly/AS7/JPA > deployment don't you still have to specify the SQL dialect in your > persistence.xml? Or is this automatically figured out now? > > I have a user that is seeing postgres org.postgresql.util.PSQLException: > ERROR: operator does not exist > > Errors and I thought setting the dialect might yelp. > > Thanks. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > 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
