DataNucleus

Revision: 10242
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10242&view=rev
Author:   andy_jefferson
Date:     2010-06-17 15:25:42 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
[NUCRDBMS-419] patch to set "resultDistinct" in generic compilation so that its available for cached compilations

Modified Paths:
--------------
    platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/query/JDOQLQuery.java

Modified: platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/query/JDOQLQuery.java
===================================================================
--- platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/query/JDOQLQuery.java	2010-06-17 08:39:44 UTC (rev 10241)
+++ platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/query/JDOQLQuery.java	2010-06-17 15:25:42 UTC (rev 10242)
@@ -264,6 +264,7 @@
             if (datastoreCompilation != null)
             {
                 // Cached compilation exists for this datastore so reuse it
+                setResultDistinct(compilation.getResultDistinct());
                 return;
             }
         }
@@ -812,6 +813,7 @@
         if (!getResultDistinct() && stmt.isDistinct())
         {
             setResultDistinct(true);
+            compilation.setResultDistinct();
         }
 
         if (candidateCollection != null)


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10241
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10241&view=rev
Author:   andy_jefferson
Date:     2010-06-17 08:39:44 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
proviso on insert batching

Modified Paths:
--------------
    documentation/accessplatform.datanucleus.org/trunk/docs/rdbms/statement_batching.xml

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/rdbms/statement_batching.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/rdbms/statement_batching.xml	2010-06-17 08:29:06 UTC (rev 10240)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/rdbms/statement_batching.xml	2010-06-17 08:39:44 UTC (rev 10241)
@@ -43,7 +43,8 @@
                 The statements that DataNucleus currently allows for batching are
             </p>
             <ul>
-                <li>Insert of objects (from version 2.1.1)</li>
+                <li>Insert of objects (from version 2.1.1). This is not enabled when objects being inserted are
+                    using <i>identity</i> value generation strategy</li>
                 <li>Delete of objects</li>
                 <li>Insert of container elements/keys/values</li>
                 <li>Delete of container elements/keys/values</li>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10240
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10240&view=rev
Author:   andy_jefferson
Date:     2010-06-17 08:29:06 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
move queryCache props under cache

Modified Paths:
--------------
    documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml	2010-06-17 08:13:01 UTC (rev 10239)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml	2010-06-17 08:29:06 UTC (rev 10240)
@@ -1570,8 +1570,89 @@
                     </tr>
                 </table>
                 <br/>
+                <a name="QueryCache"/>
+                <table>
+                    <tr>
+                        <th colspan="2">
+                            <B>datanucleus.cache.queryCompilation.type</B>
+                        </th>
+                    </tr>
+                    <tr>
+                        <td width="120">Description</td>
+                        <td>Type of cache to use for caching of generic query compilations</td>
+                    </tr>
+                    <tr>
+                        <td>Range of Values</td>
+                        <td>none | <B>soft</B> | weak | strong | {your-plugin-name}</td>
+                    </tr>
+                </table>
                 <br/>
+                <table>
+                    <tr>
+                        <th colspan="2">
+                            <B>datanucleus.cache.queryCompilationDatastore.type</B>
+                        </th>
+                    </tr>
+                    <tr>
+                        <td width="120">Description</td>
+                        <td>Type of cache to use for caching of datastore query compilations</td>
+                    </tr>
+                    <tr>
+                        <td>Range of Values</td>
+                        <td>none | <B>soft</B> | weak | strong | {your-plugin-name}</td>
+                    </tr>
+                </table>
                 <br/>
+                <table>
+                    <tr>
+                        <th colspan="2">
+                            <B>datanucleus.cache.queryResults.type</B>
+                        </th>
+                    </tr>
+                    <tr>
+                        <td width="120">Description</td>
+                        <td>Type of cache to use for caching query results.</td>
+                    </tr>
+                    <tr>
+                        <td>Range of Values</td>
+                        <td>none | <B>soft</B> | weak | strong | javax.cache | memcache | {your-plugin-name}</td>
+                    </tr>
+                </table>
+                <br/>
+                <table>
+                    <tr>
+                        <th colspan="2">
+                            <B>datanucleus.cache.queryResults.cacheName</B>
+                        </th>
+                    </tr>
+                    <tr>
+                        <td width="120">Description</td>
+                        <td>Name of cache for caching the query results.</td>
+                    </tr>
+                    <tr>
+                        <td>Range of Values</td>
+                        <td><B>datanucleus-query</B> | {your-name}</td>
+                    </tr>
+                </table>
+                <br/>
+                <table>
+                    <tr>
+                        <th colspan="2">
+                            <B>datanucleus.cache.queryResults.maxSize</B>
+                        </th>
+                    </tr>
+                    <tr>
+                        <td width="120">Description</td>
+                        <td>Max size for the query results cache (supported by weak, soft, strong)</td>
+                    </tr>
+                    <tr>
+                        <td>Range of Values</td>
+                        <td><b>-1</b> | integer value</td>
+                    </tr>
+                </table>
+                <br/>
+                <br/>
+                <br/>
             </subsection>
 
             <a name="identity"/>
@@ -1856,90 +1937,9 @@
 
             <a name="query"/>
             <subsection name="Query control">
-                <a name="QueryCache"/>
                 <table>
                     <tr>
                         <th colspan="2">
-                            <B>datanucleus.cache.queryCompilation.type</B>
-                        </th>
-                    </tr>
-                    <tr>
-                        <td width="120">Description</td>
-                        <td>Type of cache to use for caching of generic query compilations</td>
-                    </tr>
-                    <tr>
-                        <td>Range of Values</td>
-                        <td>none | <B>soft</B> | weak | strong | {your-plugin-name}</td>
-                    </tr>
-                </table>
-                <br/>
-                <table>
-                    <tr>
-                        <th colspan="2">
-                            <B>datanucleus.cache.queryCompilationDatastore.type</B>
-                        </th>
-                    </tr>
-                    <tr>
-                        <td width="120">Description</td>
-                        <td>Type of cache to use for caching of datastore query compilations</td>
-                    </tr>
-                    <tr>
-                        <td>Range of Values</td>
-                        <td>none | <B>soft</B> | weak | strong | {your-plugin-name}</td>
-                    </tr>
-                </table>
-                <br/>
-                <table>
-                    <tr>
-                        <th colspan="2">
-                            <B>datanucleus.cache.queryResults.type</B>
-                        </th>
-                    </tr>
-                    <tr>
-                        <td width="120">Description</td>
-                        <td>Type of cache to use for caching query results.</td>
-                    </tr>
-                    <tr>
-                        <td>Range of Values</td>
-                        <td>none | <B>soft</B> | weak | strong | javax.cache | memcache | {your-plugin-name}</td>
-                    </tr>
-                </table>
-                <br/>
-                <table>
-                    <tr>
-                        <th colspan="2">
-                            <B>datanucleus.cache.queryResults.cacheName</B>
-                        </th>
-                    </tr>
-                    <tr>
-                        <td width="120">Description</td>
-                        <td>Name of cache for caching the query results.</td>
-                    </tr>
-                    <tr>
-                        <td>Range of Values</td>
-                        <td><B>datanucleus-query</B> | {your-name}</td>
-                    </tr>
-                </table>
-                <br/>
-                <table>
-                    <tr>
-                        <th colspan="2">
-                            <B>datanucleus.cache.queryResults.maxSize</B>
-                        </th>
-                    </tr>
-                    <tr>
-                        <td width="120">Description</td>
-                        <td>Max size for the query results cache (supported by weak, soft, strong)</td>
-                    </tr>
-                    <tr>
-                        <td>Range of Values</td>
-                        <td><b>-1</b> | integer value</td>
-                    </tr>
-                </table>
-                <br/>
-                <table>
-                    <tr>
-                        <th colspan="2">
                             <B>datanucleus.query.flushBeforeExecution</B>
                         </th>
                     </tr>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10239
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10239&view=rev
Author:   andy_jefferson
Date:     2010-06-17 08:13:01 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
PolePos

Modified Paths:
--------------
    documentation/datanucleus.org/trunk/performance/index.xml

Modified: documentation/datanucleus.org/trunk/performance/index.xml
===================================================================
--- documentation/datanucleus.org/trunk/performance/index.xml	2010-06-17 07:03:39 UTC (rev 10238)
+++ documentation/datanucleus.org/trunk/performance/index.xml	2010-06-17 08:13:01 UTC (rev 10239)
@@ -48,6 +48,36 @@
                 For performance of DataNucleus Access Platform, please refer to the
                 <a href="../products/accessplatform/performance_tuning.html">Performance Tuning Guide</a>
             </p>
+
+            <subsection name="PolePosition">
+                <p>
+                    The <a href="http://www.polepos.org">PolePosition</a> benchmark is a project on SourceForge
+                    to provide a benchmark of the write, read and delete of different data structures using the
+                    various persistence tools on the market. JPOX was run against this benchmark just before
+                    being renamed as DataNucleus and the results are found 
+                    <a href="http://www.datanucleus.org/servlet/wiki/display/ENG/Polepos">in the DataNucleus Wiki</a>.
+                    The input data used for that benchmark run is found 
+                    <a href="http://jpox.svn.sourceforge.net/viewvc/jpox/benchmark/polepos/trunk/">in JPOX SVN</a>.
+                </p>
+                <p>
+                    Some comments on the PolePos benchmark :-
+                </p>
+                <ul>
+                    <li>It is essential that tests for such as Hibernate and DataNucleus performance comparable
+                    things. Some of the original tests had the "delete" simply doing a "DELETE FROM TBL" for Hibernate
+                    yet doing an Extent followed by delete each object individually for a JDO implementation. This is
+                    an unfair comparison and in the source tree in JPOX SVN this is corrected</li>
+                    <li>It is essential that schema is generated before the test, otherwise the test is no longer
+                    a benchmark of just a persistence operation. The source tree in JPOX SVN assumes the schema
+                    exists</li>
+                    <li>Each persistence implementation should have its own tuning options, and be able to add 
+                    things like discriminators since that is what would happen in a real application. The source
+                    tree in JPOX SVN does this for JPOX running. Similarly a JDO implementation would tune the
+                    fetch groups being used - this is not present in the SourceForge project but is in JPOX SVN</li>
+                    <li>DataNucleus performance is considered to be significantly improved over JPOX particularly
+                    due to batched inserts, and due to a rewritten query implementation that does enhanced fetching.</li>
+                </ul>
+            </subsection>
         </section>
 
     </body>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10238
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10238&view=rev
Author:   andy_jefferson
Date:     2010-06-17 07:03:39 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
[NUCRDBMS-412] HSQLDB 2.0 allows getGeneratedKeys()

Modified Paths:
--------------
    platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/adapter/HSQLAdapter.java

Modified: platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/adapter/HSQLAdapter.java
===================================================================
--- platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/adapter/HSQLAdapter.java	2010-06-17 06:46:59 UTC (rev 10237)
+++ platform/store.rdbms/trunk/src/java/org/datanucleus/store/rdbms/adapter/HSQLAdapter.java	2010-06-17 07:03:39 UTC (rev 10238)
@@ -61,11 +61,11 @@
         supportedOptions.add(IDENTITY_COLUMNS);
         supportedOptions.add(SEQUENCES);
         supportedOptions.add(UNIQUE_IN_END_CREATE_STATEMENTS);
-        supportedOptions.remove(GET_GENERATED_KEYS_STATEMENT);
         if (datastoreMajorVersion < 2)
         {
-            // HSQL 2.0 introduced support for batching
+            // HSQL 2.0 introduced support for batching and use of getGeneratedKeys
             supportedOptions.remove(STATEMENT_BATCHING);
+            supportedOptions.remove(GET_GENERATED_KEYS_STATEMENT);
         }
         supportedOptions.remove(DEFERRED_CONSTRAINTS);
         supportedOptions.remove(CHECK_IN_CREATE_STATEMENTS);


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10237
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10237&view=rev
Author:   andy_jefferson
Date:     2010-06-17 06:46:59 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
defaults for JDO increment/sequence allocation size

Modified Paths:
--------------
    documentation/accessplatform.datanucleus.org/trunk/docs/migration.xml

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/migration.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/migration.xml	2010-06-17 06:37:32 UTC (rev 10236)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/migration.xml	2010-06-17 06:46:59 UTC (rev 10237)
@@ -21,8 +21,14 @@
             <a name="2_1_1_FROM_2_1_0_REL"/>
             <subsection name="Migration from 2.1.0 Release to 2.1.1">
                 <p>
-                    Migrating from AccessPlatform 2.1.0 Release to 2.1.1 will require no changes.
+                    Migrating from AccessPlatform 2.1.0 Release to 2.1.1 will require the following changes.
                 </p>
+                <ul>
+                    <li>Default allocation size for <i>increment</i> and <i>sequence</i> value strategies have
+                        been changed for JDO usage to 10 and 10 respectively (from 5 and 1). You can configure
+                        the global defaults via persistence properties</li>
+                </ul>
+                <br/>
             </subsection>
 
             <a name="2_1_0_REL_FROM_2_1_0_M3"/>
@@ -35,6 +41,7 @@
                     <li>Dropped support for class-level metadata extension "cacheable"; use standardised
                         <i>cacheable</i> attribute (or annotation) instead.</li>
                 </ul>
+                <br/>
             </subsection>
 
             <a name="2_1_0_M3_FROM_2_1_0_M2"/>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10236
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10236&view=rev
Author:   andy_jefferson
Date:     2010-06-17 06:37:32 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
[NUCRDBMS-418] set defaults to 10 and 10 for JDO

Modified Paths:
--------------
    documentation/accessplatform.datanucleus.org/trunk/docs/jdo/value_generation.xml
    documentation/accessplatform.datanucleus.org/trunk/docs/jpa/value_generation.xml

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/jdo/value_generation.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/jdo/value_generation.xml	2010-06-17 06:30:46 UTC (rev 10235)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/jdo/value_generation.xml	2010-06-17 06:37:32 UTC (rev 10236)
@@ -168,11 +168,12 @@
                         <td>key-start-with</td>
                         <td>the initial value for the sequence</td>
                         <td>No</td>
-                    </tr>	                    	                    
+                    </tr>
                     <tr>
                         <td>key-increment-by</td>
-                        <td>specifies which value is added to the current sequence value to create a new value. default is 1</td>
-                        <td>No</td>
+                        <td>specifies which value is added to the current sequence value to create a new value.
+                            Refer to persistence property <b>datanucleus.valuegeneration.sequence.allocationSize</b></td>
+                        <td>No. Default is 10.</td>
                     </tr>
                     <tr>
                         <td>key-database-cache-size</td>
@@ -304,8 +305,9 @@
                         <td>key-cache-size</td>
                         <td>number of unique identifiers to cache. The keys are pre-allocated, cached 
                             and used on demand. If <i>key-cache-size</i> is greater than 1, it may generate holes in the 
-                            object keys in the database, if not all keys are used.</td>
-                        <td>No. Defaults to 5</td>
+                            object keys in the database, if not all keys are used.
+                            Refer to persistence property <b>datanucleus.valuegeneration.increment.allocationSize</b></td>
+                        <td>No. Defaults to 10</td>
                     </tr>
                     <tr>
                         <td>sequence-table-basis</td>

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/jpa/value_generation.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/jpa/value_generation.xml	2010-06-17 06:30:46 UTC (rev 10235)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/jpa/value_generation.xml	2010-06-17 06:37:32 UTC (rev 10236)
@@ -136,8 +136,8 @@
                     </tr>	                    	                    
                     <tr>
                         <td>key-increment-by</td>
-                        <td>specifies which value is added to the current sequence value to create a new value. default is 1</td>
-                        <td>No</td>
+                        <td>specifies which value is added to the current sequence value to create a new value.</td>
+                        <td>No. Default is 50</td>
                     </tr>
                     <tr>
                         <td>key-database-cache-size</td>
@@ -257,7 +257,7 @@
                         <td>number of unique identifiers to cache. The keys are pre-allocated, cached 
                             and used on demand. If <i>key-cache-size</i> is greater than 1, it may generate holes in the 
                             object keys in the database, if not all keys are used.</td>
-                        <td>No. Defaults to 5</td>
+                        <td>No. Default is 50</td>
                     </tr>
                     <tr>
                         <td>sequence-table-basis</td>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

Revision: 10235
          http://datanucleus.svn.sourceforge.net/datanucleus/?rev=10235&view=rev
Author:   andy_jefferson
Date:     2010-06-17 06:30:46 +0000 (Thu, 17 Jun 2010)

Log Message:
-----------
[NUCRDBMS-418] set defaults to 10 and 10

Modified Paths:
--------------
    documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml
    platform/core/trunk/plugin.xml

Modified: documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml
===================================================================
--- documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml	2010-06-16 18:29:02 UTC (rev 10234)
+++ documentation/accessplatform.datanucleus.org/trunk/docs/persistence_properties.xml	2010-06-17 06:30:46 UTC (rev 10235)
@@ -1628,7 +1628,7 @@
                     </tr>
                     <tr>
                         <td>Range of Values</td>
-                        <td>1 | (integer value)</td>
+                        <td>10 | (integer value)</td>
                     </tr>
                 </table>
                 <br/>
@@ -1646,7 +1646,7 @@
                     </tr>
                     <tr>
                         <td>Range of Values</td>
-                        <td>5 | (integer value)</td>
+                        <td>10 | (integer value)</td>
                     </tr>
                 </table>
                 <br/>

Modified: platform/core/trunk/plugin.xml
===================================================================
--- platform/core/trunk/plugin.xml	2010-06-16 18:29:02 UTC (rev 10234)
+++ platform/core/trunk/plugin.xml	2010-06-17 06:30:46 UTC (rev 10235)
@@ -189,9 +189,9 @@
             validator="org.datanucleus.properties.CorePropertyValidator"/>
         <persistence-property name="datanucleus.valuegeneration.transactionAttribute" value="New"
             validator="org.datanucleus.properties.CorePropertyValidator"/>
-        <persistence-property name="datanucleus.valuegeneration.sequence.allocationSize" value="1"
+        <persistence-property name="datanucleus.valuegeneration.sequence.allocationSize" value="10"
             validator="org.datanucleus.properties.IntegerPropertyValidator"/>
-        <persistence-property name="datanucleus.valuegeneration.increment.allocationSize" value="5"
+        <persistence-property name="datanucleus.valuegeneration.increment.allocationSize" value="10"
             validator="org.datanucleus.properties.IntegerPropertyValidator"/>
 
         <!-- All properties below here are datastore level -->
@@ -959,4 +959,4 @@
        <entityresolver url="/org/datanucleus/jdo/jdo_2_2.xsd"/>
        <entityresolver url="/org/datanucleus/jpa/jpa_persistence_1_0.xsd"/>
     </extension>
-</plugin>
\ No newline at end of file
+</plugin>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.