-
Notifications
You must be signed in to change notification settings - Fork 3.5k
/
appendix-Configuration_Properties.xml
435 lines (429 loc) · 19.9 KB
/
appendix-Configuration_Properties.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
<?xml version='1.0' encoding='utf-8' ?>
<appendix xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Configuration properties</title>
<section xml:id="config-strategy">
<title>Strategy configurations</title>
<para>
Many configuration settings define pluggable strategies that Hibernate uses for various purposes.
The configuration of many of these strategy type settings accept definition in various forms. The
documentation of such configuration settings refer here. The types of forms available in such cases
include:
</para>
<variablelist>
<varlistentry>
<term>short name (if defined)</term>
<listitem>
<para>
Certain built-in strategy implementations have a corresponding short name.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>strategy instance</term>
<listitem>
<para>
An instance of the strategy implementation to use can be specified
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>strategy Class reference</term>
<listitem>
<para>
A <classname>java.lang.Class</classname> reference of the strategy implementation to use can
be specified
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>strategy Class name</term>
<listitem>
<para>
The class name (<classname>java.lang.String</classname>) of the strategy implementation to
use can be specified
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section>
<title>General Configuration</title>
<informaltable>
<tgroup cols="3">
<colspec colwidth="100px" />
<colspec colwidth="120px" />
<colspec colwidth="250px" />
<tbody>
<row>
<entry>hibernate.dialect</entry>
<entry>A fully-qualified classname</entry>
<entry>
<para>
The classname of a Hibernate <classname>org.hibernate.dialect.Dialect</classname> from which Hibernate
can generate SQL optimized for a particular relational database.
</para>
<para>
In most cases Hibernate can choose the correct <classname>org.hibernate.dialect.Dialect</classname>
implementation based on the JDBC metadata returned by the JDBC driver.
</para>
</entry>
</row>
<row>
<entry>hibernate.show_sql</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Write all SQL statements to the console. This is an alternative to setting the log category
<property>org.hibernate.SQL</property> to debug.</entry>
</row>
<row>
<entry>hibernate.format_sql</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Pretty-print the SQL in the log and console.</entry>
</row>
<row>
<entry>hibernate.default_schema</entry>
<entry>A schema name</entry>
<entry>Qualify unqualified table names with the given schema or tablespace in generated SQL.</entry>
</row>
<row>
<entry>hibernate.default_catalog</entry>
<entry>A catalog name</entry>
<entry>Qualifies unqualified table names with the given catalog in generated SQL.</entry>
</row>
<row>
<entry>hibernate.session_factory_name</entry>
<entry>A JNDI name</entry>
<entry>The <classname>org.hibernate.SessionFactory</classname> is automatically bound to this name in JNDI
after it is created.</entry>
</row>
<row>
<entry>hibernate.max_fetch_depth</entry>
<entry>A value between <literal>0</literal> and <literal>3</literal></entry>
<entry>Sets a maximum depth for the outer join fetch tree for single-ended associations. A single-ended
assocation is a one-to-one or many-to-one assocation. A value of <literal>0</literal> disables default outer
join fetching.</entry>
</row>
<row>
<entry>hibernate.default_batch_fetch_size</entry>
<entry><para><literal>4</literal>,<literal>8</literal>, or <literal>16</literal></para></entry>
<entry>Default size for Hibernate batch fetching of associations.</entry>
</row>
<row>
<entry>hibernate.default_entity_mode</entry>
<entry><para><literal>dynamic-map</literal> or <literal>pojo</literal></para></entry>
<entry>Default mode for entity representation for all sessions opened from this
<classname>SessionFactory</classname>, defaults to <literal>pojo</literal>.</entry>
</row>
<row>
<entry>hibernate.order_updates</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Forces Hibernate to order SQL updates by the primary key value of the items being updated. This
reduces the likelihood of transaction deadlocks in highly-concurrent systems.</entry>
</row>
<row>
<entry>hibernate.order_by.default_null_ordering</entry>
<entry><para><literal>none</literal>, <literal>first</literal> or <literal>last</literal></para></entry>
<entry>Defines precedence of null values in <literal>ORDER BY</literal> clause. Defaults to
<literal>none</literal> which varies between RDBMS implementation.</entry>
</row>
<row>
<entry>hibernate.generate_statistics</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Causes Hibernate to collect statistics for performance tuning.</entry>
</row>
<row>
<entry>hibernate.use_identifier_rollback</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>If true, generated identifier properties are reset to default values when objects are
deleted.</entry>
</row>
<row>
<entry>hibernate.use_sql_comments</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>If true, Hibernate generates comments inside the SQL, for easier debugging.</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<section>
<title>Database configuration</title>
<table>
<title>JDBC properties</title>
<tgroup cols="3">
<thead>
<row>
<entry>Property</entry>
<entry>Example</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>hibernate.jdbc.fetch_size</entry>
<entry><literal>0</literal> or an integer</entry>
<entry>A non-zero value determines the JDBC fetch size, by calling
<methodname>Statement.setFetchSize()</methodname>.</entry>
</row>
<row>
<entry>hibernate.jdbc.batch_size</entry>
<entry><para>A value between <literal>5</literal> and <literal>30</literal></para></entry>
<entry>A non-zero value causes Hibernate to use JDBC2 batch updates.</entry>
</row>
<row>
<entry>hibernate.jdbc.batch_versioned_data</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry><para>Set this property to <literal>true</literal> if your JDBC driver returns correct row counts
from <methodname>executeBatch()</methodname>. This option is usually safe, but is disabled by default. If
enabled, Hibernate uses batched DML for automatically versioned data.</para></entry>
</row>
<row>
<entry>hibernate.jdbc.factory_class</entry>
<entry>The fully-qualified class name of the factory</entry>
<entry><para>Select a custom <classname>org.hibernate.jdbc.Batcher</classname>. Irrelevant for most
applications.</para></entry>
</row>
<row>
<entry>hibernate.jdbc.use_scrollable_resultset</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Enables Hibernate to use JDBC2 scrollable resultsets. This property is only relevant for
user-supplied JDBC connections. Otherwise, Hibernate uses connection metadata.</entry>
</row>
<row>
<entry>hibernate.jdbc.use_streams_for_binary</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry><para>Use streams when writing or reading <type>binary</type> or <type>serializable</type> types to
or from JDBC. This is a system-level property.</para></entry>
</row>
<row>
<entry>hibernate.jdbc.use_get_generated_keys</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry><para>Allows Hibernate to use JDBC3 <classname>PreparedStatement.getGeneratedKeys()</classname> to
retrieve natively-generated keys after insert. You need the JDBC3+ driver and JRE1.4+. Disable this property
if your driver has problems with the Hibernate identifier generators. By default, it tries to detect the
driver capabilities from connection metadata.</para></entry>
</row>
</tbody>
</tgroup>
</table>
<table>
<title>Cache Properties</title>
<tgroup cols="3">
<colspec colwidth="100px" />
<colspec colwidth="100px" />
<colspec colwidth="240px" />
<thead>
<row>
<entry>Property</entry>
<entry>Example</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>hibernate.cache.provider_class</entry>
<entry>Fully-qualified classname</entry>
<entry>The classname of a custom CacheProvider.</entry>
</row>
<row>
<entry>hibernate.cache.use_minimal_puts</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Optimizes second-level cache operation to minimize writes, at the cost of more frequent reads. This
is most useful for clustered caches and is enabled by default for clustered cache implementations.</entry>
</row>
<row>
<entry>hibernate.cache.use_query_cache</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Enables the query cache. You still need to set individual queries to be cachable.</entry>
</row>
<row>
<entry>hibernate.cache.use_second_level_cache</entry> <entry><para><literal>true</literal> or
<literal>false</literal></para></entry> <entry>Completely disable the second level cache, which is enabled
by default for classes which specify a <cache> mapping.</entry>
</row>
<row>
<entry>hibernate.cache.query_cache_factory</entry>
<entry>Fully-qualified classname</entry>
<entry>A custom <interfacename>QueryCache</interfacename> interface. The default is the built-in
<interfacename>StandardQueryCache</interfacename>.</entry>
</row>
<row>
<entry>hibernate.cache.region_prefix</entry>
<entry>A string</entry>
<entry>A prefix for second-level cache region names.</entry>
</row>
<row>
<entry>hibernate.cache.use_structured_entries</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Forces Hibernate to store data in the second-level cache in a more human-readable format.</entry>
</row>
<row>
<entry>hibernate.cache.use_reference_entries</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Optimizes second-level cache operation to store immutable entities (aka "reference") which do
not have associations into cache directly, this case, lots of disasseble and deep copy operations
can be avoid.
Default value of this property is <literal>false</literal>.
</entry>
</row>
</tbody>
</tgroup>
</table>
<table>
<title>Transactions properties</title>
<tgroup cols="3">
<colspec colwidth="100px" />
<colspec colwidth="100px" />
<colspec colwidth="240px" />
<thead>
<row>
<entry>Property</entry>
<entry>Example</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>hibernate.transaction.factory_class</entry>
<entry>
<para><property>jdbc</property> or <property></property></para>
</entry>
<entry>
<para>
Names the <interfacename>org.hibernate.engine.transaction.spi.TransactionFactory</interfacename>
strategy implementation to use. See <xref linkend="config-strategy"/> and
<xref linkend="services-TransactionFactory"/>
</para>
</entry>
</row>
<row>
<entry>jta.UserTransaction</entry>
<entry>A JNDI name</entry>
<entry><para>The <classname>JTATransactionFactory</classname> needs a JNDI name to obtain the JTA
UserTransaction from the application server.</para></entry>
</row>
<row>
<entry>hibernate.transaction.manager_lookup_class</entry>
<entry>A fully-qualified classname</entry>
<entry><para>The classname of a <classname>TransactionManagerLookup</classname>, which is used in
conjunction with JVM-level or the hilo generator in a JTA environment.</para></entry>
</row>
<row>
<entry>hibernate.transaction.flush_before_completion</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Causes the session be flushed during the <phrase>before completion</phrase> phase of the
transaction. If possible, use built-in and automatic session context management instead.</entry>
</row>
<row>
<entry>hibernate.transaction.auto_close_session</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>Causes the session to be closed during the <phrase>after completion</phrase> phase of the
transaction. If possible, use built-in and automatic session context management instead.</entry>
</row>
</tbody>
</tgroup>
</table>
<note>
<para>
Each of the properties in the following table are prefixed by <literal>hibernate.</literal>. It has been removed
in the table to conserve space.
</para>
</note>
<table>
<title>Miscellaneous properties</title>
<tgroup cols="3">
<thead>
<row>
<entry>Property</entry>
<entry>Example</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>current_session_context_class</entry>
<entry><para>One of <literal>jta</literal>, <literal>thread</literal>, <literal>managed</literal>, or
<literal>custom.Class</literal></para></entry>
<entry><para>Supply a custom strategy for the scoping of the <classname>Current</classname>
Session.</para></entry>
</row>
<row>
<entry>factory_class</entry>
<entry><para><literal>org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory</literal> or
<literal>org.hibernate.hql.internal.classic.ClassicQueryTranslatorFactory</literal></para></entry>
<entry>Chooses the HQL parser implementation.</entry>
</row>
<row>
<entry>query.substitutions</entry>
<entry><para><literal>hqlLiteral=SQL_LITERAL</literal> or <literal>hqlFunction=SQLFUNC</literal>
</para></entry>
<entry>Map from tokens in Hibernate queries to SQL tokens, such as function or literal names.</entry>
</row>
<row>
<entry>hbm2ddl.auto</entry>
<entry><para><literal>validate</literal>, <literal>update</literal>, <literal>create</literal>,
<literal>create-drop</literal></para></entry>
<entry>Validates or exports schema DDL to the database when the <classname>SessionFactory</classname> is
created. With <command>create-drop</command>, the database schema is dropped when the
<classname>SessionFactory</classname> is closed explicitly.</entry>
</row>
<row>
<entry>cglib.use_reflection_optimizer</entry>
<entry><para><literal>true</literal> or <literal>false</literal></para></entry>
<entry>If enabled, Hibernate uses CGLIB instead of runtime reflection. This is a system-level
property. Reflection is useful for troubleshooting. Hibernate always requires CGLIB even if you disable the
optimizer. You cannot set this property in hibernate.cfg.xml.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>Connection pool properties</title>
<itemizedlist>
<title>c3p0 connection pool properties</title>
<listitem><para>hibernate.c3p0.min_size</para></listitem>
<listitem><para>hibernate.c3p0.max_size</para></listitem>
<listitem><para>hibernate.c3p0.timeout</para></listitem>
<listitem><para>hibernate.c3p0.max_statements</para></listitem>
</itemizedlist>
<table>
<title>Proxool connection pool properties</title>
<tgroup cols="2">
<colspec colwidth="100px" />
<colspec colwidth="340px" />
<thead>
<row>
<entry>Property</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>hibernate.proxool.xml</entry>
<entry>Configure Proxool provider using an XML file (.xml is appended automatically)</entry>
</row>
<row>
<entry>hibernate.proxool.properties</entry>
<entry>Configure the Proxool provider using a properties file (.properties is appended
automatically)</entry>
</row>
<row>
<entry>hibernate.proxool.existing_pool</entry>
<entry>Whether to configure the Proxool provider from an existing pool</entry>
</row>
<row>
<entry>hibernate.proxool.pool_alias</entry>
<entry>Proxool pool alias to use. Required.</entry>
</row>
</tbody>
</tgroup>
</table>
<note>
<para>
For information on specific configuration of Proxool, refer to the Proxool documentation available from
<link xlink:href="http://proxool.sourceforge.net/" />.
</para>
</note>
</section>
</appendix>