Author: tolusha
Date: 2011-12-01 08:27:39 -0500 (Thu, 01 Dec 2011)
New Revision: 5251
Modified:
jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml
Log:
EXOJCR-1665: docs about using LIMIT and OFFSET clauses in DB2
Modified:
jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml
===================================================================
---
jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml 2011-12-01
09:05:19 UTC (rev 5250)
+++
jcr/trunk/exo.jcr.docs/exo.jcr.docs.developer/en/src/main/docbook/en-US/modules/jcr/configuration/jdbc-data-container-config.xml 2011-12-01
13:27:39 UTC (rev 5251)
@@ -102,6 +102,12 @@
expect any support and if performances in read accesses are more
important than the consistency in your use-case. This dialect is only
dedicated to the community.</para>
+ </note><note>
+ <para>RDBMS reindexing feature use queries based on LIMIT and OFFSET
+ clauses which are not enabled by default for DB2. However, you can
+ ensure they are enabled by executing the following <programlisting>$ db2set
DB2_COMPATIBILITY_VECTOR=MYS
+$ db2stop
+$ db2start</programlisting></para>
</note> Each database software supports ANSI SQL standards but also has
its own specifics. So, each database has its own configuration in eXo JCR
as a database dialect parameter. If you need a more detailed configuration
Show replies by date