HHH-5397 - Odds and ends from documentation merge : fixed <programlisting/> rendering issue
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@19991 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
0303d88761
commit
48a5e04caa
|
@ -78,7 +78,10 @@
|
|||
Starting with version 3.3, Hibernate has a fare more powerful way to automatically determine
|
||||
which dialect to should be used by relying on a series of delegates which implement the
|
||||
<interfacename>org.hibernate.dialect.resolver.DialectResolver</interfacename> which defines only a
|
||||
single method:<programlisting role="JAVA"><![CDATA[public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException]]></programlisting>.
|
||||
single method:
|
||||
</para>
|
||||
<programlisting role="JAVA"><![CDATA[public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException]]></programlisting>
|
||||
<para>
|
||||
The basic contract here is that if the resolver 'understands' the given database metadata then
|
||||
it returns the corresponding Dialect; if not it returns null and the process continues to the next
|
||||
resolver. The signature also identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</exceptionname>
|
||||
|
|
Loading…
Reference in New Issue