Any JDO-enabled application will require at least one PersistenceManagerFactory which accepts properties to define its capabilities. Any JPA-enabled application will require at least one EntityManagerFactory which also accepts properties to define its capabilities. DataNucleus provides a large number of properties for use with either JDO or JPA APIs.

Use of the following properties gives you more control over the operations of DataNucleus, but bear in mind that these properties are only for use with DataNucleus and will not work with other JDO/JPA implementations. Please note that as of 2.0 M4, all persistence property names are case-insensitive

• Datastore Definition - datastore properties
• General - general properties
• Schema Control - properties controlling the generation of the datastore schema.
• Transactions and Locking - properties controlling how transactions operate
• Caching - properties controlling the behaviour of the cache(s)
• Value Generation - properties controlling the generation of object identities and field values
• MetaData - metadata properties
• Auto-Start - Auto-Start Mechanism properties
• Query - properties controlling the behaviour of queries

Please note that there are additional persistence properties for each supported datastore. See RDBMS and DB4O

Datastore Definition

datanucleus.ConnectionFactory
Description	Instance of a connection factory for transactional connections. For RDBMS, it must be an instance of javax.sql.DataSource. See Data Sources.
Range of Values

datanucleus.ConnectionFactory2
Description	Instance of a connection factory for nontransactional connections. For RDBMS, it must be an instance of javax.sql.DataSource. See Data Sources.
Range of Values

datanucleus.ConnectionFactoryName
Description	The JNDI name for a connection factory for transactional connections. For RBDMS, it must be a JNDI name that points to a javax.sql.DataSource object. See Data Sources.
Range of Values

datanucleus.ConnectionFactory2Name
Description	The JNDI name for a connection factory for nontransactional connections. For RBDMS, it must be a JNDI name that points to a javax.sql.DataSource object. See Data Sources.
Range of Values

datanucleus.ConnectionURL
Description	URL specifying the datastore to use for persistence
Range of Values

datanucleus.ConnectionDriverName
Description	The name of the (JDBC) driver to use for the DB (for RDBMS only).
Range of Values

datanucleus.ConnectionUserName
Description	Username to use for connecting to the DB
Range of Values

datanucleus.ConnectionPassword
Description	Password to use for connecting to the DB. See datanucleus.ConnectionPasswordDecrypter for a way of providing an encrypted password here
Range of Values

datanucleus.ConnectionPasswordDecrypter
Description	Name of a class that implements org.datanucleus.store.connection.DecryptionProvider and should only be specified if the password is encrypted in the persistence properties
Range of Values

General

datanucleus.IgnoreCache
Description	Whether to ignore the cache for queries
Range of Values	true | false

datanucleus.Multithreaded
Description	Whether to run the PersistenceManager multithreaded. Note that this is a hint only to try to allow thread-safe operations on the PM
Range of Values	true | false

datanucleus.NontransactionalRead
Description	Whether to allow nontransactional reads
Range of Values	false | true

datanucleus.NontransactionalWrite
Description	Whether to allow nontransactional writes
Range of Values	false | true

datanucleus.Optimistic
Description	Whether to use Optimistic transactions For JDO this defaults to false and for JPA it defaults to true
Range of Values	true | false

datanucleus.RetainValues
Description	Whether to suppress the clearing of values from persistent instances on transaction completion
Range of Values	true | false

datanucleus.RestoreValues
Description	Whether persistent object have transactional field values restored when transaction rollback occurs.
Range of Values	true | false

datanucleus.Mapping
Description	Name for the ORM MetaData mapping files to use with this PMF. For example if this is set to "mysql" then the implementation looks for MetaData mapping files called "{classname}-mysql.orm" or "package-mysql.orm". If this is not specified then the JDO implementation assumes that all is specified in the JDO MetaData file. RDBMS datastores only
Range of Values

datanucleus.mapping.Catalog
Description	Name of the catalog to use by default for all classes persisted using this PMF/EMF. This can be overridden in the MetaData where required, and is optional. DataNucleus will prefix all table names with this catalog name if the RDBMS supports specification of catalog names in DDL. RDBMS datastores only
Range of Values

datanucleus.mapping.Schema
Description	Name of the schema to use by default for all classes persisted using this PMF/EMF. This can be overridden in the MetaData where required, and is optional. DataNucleus will prefix all table names with this schema name if the RDBMS supports specification of schema names in DDL. RDBMS datastores only
Range of Values

datanucleus.DetachAllOnCommit
Description	Allows the user to select that when a transaction is committed all objects enlisted in that transaction will be automatically detached.
Range of Values	true | false

datanucleus.detachAllOnRollback
Description	Allows the user to select that when a transaction is rolled back all objects enlisted in that transaction will be automatically detached.
Range of Values	true | false

datanucleus.CopyOnAttach
Description	Whether, when attaching a detached object, we create an attached copy or simply migrate the detached object to attached state
Range of Values	true | false

datanucleus.TransactionType
Description	Type of transaction to use. If running under J2SE the default is RESOURCE_LOCAL, and if running under J2EE the default is JTA.
Range of Values	RESOURCE_LOCAL | JTA

datanucleus.ServerTimeZoneID
Description	Id of the TimeZone under which the datastore server is running. If this is not specified or is set to null it is assumed that the datastore server is running in the same timezone as the JVM under which DataNucleus is running.
Range of Values

datanucleus.PersistenceUnitName
Description	Name of a persistence-unit to be found in a persistence.xml file (under META-INF) that defines the persistence properties to use and the classes to use within the persistence process.
Range of Values

datanucleus.PersistenceUnitLoadClasses
Description	Used when we have specified the persistence-unit name for a PMF/EMF and where we want the datastore "tables" for all classes of that persistence-unit loading up into the StoreManager. Defaults to false since some databases are slow so such an operation would slow down the startup process.
Range of Values	true | false

datanucleus.persistenceXmlFilename
Description	URL name of the persistence.xml file that should be used instead of using "META-INF/persistence.xml".
Range of Values

datanucleus.datastoreReadTimeout
Description	The timeout to apply to all reads (millisecs). e.g by query or by PM.getObjectById(). Only applies if the underlying datastore supports it
Range of Values	0 | A positive value (MILLISECONDS)

datanucleus.datastoreWriteTimeout
Description	The timeout to apply to all writes (millisecs). e.g by makePersistent, or by an update. Only applies if the underlying datastore supports it
Range of Values	0 | A positive value (MILLISECONDS)

datanucleus.singletonPMFForName
Description	Whether to only allow a singleton PMF for a particular name (the name can be either the name of the PMF in jdoconfig.xml, or the name of the persistence-unit). If a subsequent request is made for a PMF with a name that already exists then a wanring will be logged and the original PMF returned.
Range of Values	true | false

datanucleus.storeManagerType
Description	Type of the StoreManager to use for this PMF/EMF. This has typical values of "rdbms", "db4o". If it isnt specified then it falls back to trying to find the StoreManager from the connection URL. The associated DataNucleus plugin has to be in the CLASSPATH when selecting this. When using data sources (as usually done in a JavaEE container), DataNucleus cannot find out the correct type automatically and this option must be set.
Range of Values	rdbms | db4o | alternate StoreManager key

datanucleus.managedRuntime
Description	Whether to allow management of the runtime of DataNucleus. Allows hooking in JMX. Please refer to the Management Guide
Range of Values	true | false

datanucleus.deletionPolicy
Description	Allows the user to decide the policy when deleting objects. The default is "JDO2" which firstly checks if the field is dependent and if so deletes dependents, and then for others will null any foreign keys out. The problem with this option is that it takes no account of whether the user has also defined <foreign-key> elements, so we provide a "DataNucleus" mode that does the dependent field part first and then if a FK element is defined will leave it to the FK in the datastore to perform any actions, and otherwise does the nulling.
Range of Values	JDO2 | DataNucleus

datanucleus.identityTranslatorType
Description	You can allow identities input to pm.getObjectById be translated into valid JDO ids if there is a suitable translator. See Identity Translator Plugin
Range of Values

datanucleus.datastoreIdentityType
Description	Which "datastore-identity" class plugin to use to represent datastore identities. Refer to Datastore Identity extensions for details.
Range of Values	datanucleus | kodo | xcalia | {user-supplied plugin}

datanucleus.attachSameDatastore
Description	When attaching an object DataNucleus by default makes no assumption about which datastore the object was detached from and so makes a check for existence before attaching each object. This option allows you to turn off that check when you know you are detaching and attaching using the same datastore.
Range of Values	false | true

datanucleus.detachAsWrapped
Description	When detaching, any mutable second class objects (Collections, Maps, Dates etc) are typically detached as the basic form (so you can use them on client-side of your application). This property allows you to select to detach as wrapped objects. It only works with "detachAllOnCommit" situations (not with detachCopy) currently
Range of Values	true | false

datanucleus.DetachOnClose
Description	This allows the user to specify whether, when a PersistenceManager/EntityManager is closed, that all objects in the L1 cache are automatically detached. Users are recommended to use the datanucleus.DetachAllOnCommit wherever possible . This will not work in JCA mode.
Range of Values	false | true

datanucleus.detachmentFields
Description	When detaching you can control what happens to loaded/unloaded fields of the FetchPlan. The default for JDO is to load any unloaded fields of the current FetchPlan before detaching. You can also unload any loaded fields that are not in the current FetchPlan (so you only get the fields you require) as well as a combination of both options
Range of Values	load-fields | unload-fields | load-unload-fields

datanucleus.manageRelationships
Description	This allows the user control over whether DataNucleus will try to manage bidirectional relations, correcting the input objects so that all relations are consistent. This process runs when flush()/commit() is called. You can set it to false if you always set both sides of a relation when persisting/updating.
Range of Values	true | false

datanucleus.manageRelationshipsChecks
Description	This allows the user control over whether DataNucleus will make consistency checks on bidirectional relations. If "datanucleus.managedRelationships" is not selected then no checks are performed. If a consistency check fails at flush()/commit() then a JDOUserException is thrown. You can set it to false if you want to omit all consistency checks.
Range of Values	true | false

datanucleus.persistenceByReachabilityAtCommit
Description	Whether to run the "persistence-by-reachability" algorithm at commit() time. This means that objects that were reachable at a call to makePersistent() but that are no longer persistent will be removed from persistence. For performance improvements, consider turning this off.
Range of Values	true | false

datanucleus.maxFetchDepth
Description	Specifies the default maximum fetch depth to use for fetching operations. The JDO2 specification defines a default of 1, and this is the DataNucleus default, meaning that only the first level of related objects will be fetched by default.
Range of Values	-1 | 1 | positive integer (non-zero)

datanucleus.classLoaderResolverName
Description	Name of a ClassLoaderResolver to use in class loading. DataNucleus provides a default that implements the JDO2 specification for class loading. This property allows the user to override this with their own class better suited to their own loading requirements.
Range of Values	jdo | {name of class-loader-resolver plugin}

datanucleus.primaryClassLoader
Description	Sets a primary classloader for situations where a primary classloader is not accessible. This ClassLoader is used when the class is not found in the default ClassLoader search path. As example, when the database driver is loaded by a different ClassLoader not in the ClassLoader search path for JDO or JPA specifications.
Range of Values	instance of java.lang.ClassLoader

datanucleus.implementationCreatorName
Description	Symbolic name of an implementation creator for "persistent interfaces" (JDO2). DataNucleus provides an implementation creator using ASM. Please note that you should have the DataNucleus Enhancer in the CLASSPATH together with ASM to use "persistent interfaces".
Range of Values	asm | none

datanucleus.plugin.pluginRegistryClassName
Description	Name of a class that acts as registry of plug-ins.
Range of Values	{fully-qualified class name}

datanucleus.plugin.pluginRegistryBundleCheck
Description	Defines what happens when plugin bundles are found and are duplicated
Range of Values	EXCEPTION | LOG | NONE

datanucleus.localisation.language
Description	Language to use for logging (e.g en, es)
Range of Values	default for JRE

datanucleus.findObject.validateWhenCached
Description	When a user calls getObjectById (JDO) or findObject (JPA) and they request validation this allows the turning off of validation when an object is found in the (L2) cache. Can be useful for performance reasons, but should be used with care. To be consistent with the JDO spec, this should be set to true
Range of Values	true | false

Schema Control

datanucleus.autoCreateSchema
Description	Whether to automatically generate any tables and constraints that don't exist. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.autoCreateTables
Description	Whether to automatically generate any tables that don't exist. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.autoCreateColumns
Description	Whether to automatically generate any columns that don't exist. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.autoCreateConstraints
Description	Whether to automatically generate any constraints that don't exist. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.autoCreateWarnOnError
Description	Whether to only log a warning when errors occur during the auto-creation/validation process. Please use with care since if the schema is incorrect errors will likely come up later and this will postpone those error checks til later, when it may be too late!!
Range of Values	true | false

datanucleus.validateTables
Description	Whether to validate tables against the persistence definition. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.validateColumns
Description	Whether to validate columns against the persistence definition. This refers to the column detail structure and NOT to whether the column exists or not. Please refer to the RDBMS Schema Guide for more details.
Range of Values	true | false

datanucleus.validateConstraints
Description	Whether to validate table constraints against the persistence definition. Please refer to the Schema Guide for more details.
Range of Values	true | false

datanucleus.readOnlyDatastore
Description	Whether the datastore is read-only or not (fixed in structure and contents).
Range of Values	true | false

datanucleus.readOnlyDatastoreAction
Description	What happens when a datastore is read-only and an object is attempted to be persisted.
Range of Values	EXCEPTION | IGNORE

datanucleus.fixedDatastore
Description	Whether the datastore is fixed in structure or not.
Range of Values	true | false

datanucleus.identifierFactory
Description	Name of the identifier factory to use when generating table/column names etc. See also the JDO RDBMS Identifier Guide.
Range of Values	datanucleus | datanucleus2 | jpox | jpa | {user-plugin-name}

datanucleus.identifier.case
Description	Which case to use in generated table and column names. See also the JDO RDBMS Identifier Guide.
Range of Values	UpperCase | LowerCase | PreserveCase

datanucleus.identifier.wordSeparator
Description	Separator character(s) to use between words in generated identifiers. Defaults to "_" (underscore)

datanucleus.identifier.tablePrefix
Description	Prefix to be prepended to all generated table names (if the identifier factory supports it)

datanucleus.identifier.tableSuffix
Description	Suffix to be appended to all generated table names (if the identifier factory supports it)

datanucleus.defaultInheritanceStrategy
Description	How to choose the inheritance strategy default for classes where no strategy has been specified. With JDO2 this will be "new-table" for base classes and "superclass-table" for subclasses. With TABLE_PER_CLASS this will be "new-table" for all classes.
Range of Values	JDO2 | TABLE_PER_CLASS

datanucleus.store.allowReferencesWithNoImplementations
Description	Whether we permit a reference field (1-1 relation) or collection of references where there are no defined implementations of the reference. False means that an exception will be thrown
Range of Values	true | false

Transactions and Locking

datanucleus.transactionIsolation
Description	Select the default transaction isolation level for ALL PersistenceManager factories. Some databases do not support all isolation levels, refer to your database documentation. Please refer to the transaction guides for JDO and JPA
Range of Values	read-uncommitted | read-committed | repeatable-read | serializable

datanucleus.SerializeRead
Description	With datastore transactions you can apply locking to objects as they are read from the datastore. This setting applies as the default for all PersistenceManagers/EntityManagers obtained. You can also specify this on a per-transaction or per-query basis (which is often better to avoid deadlocks etc)
Range of Values	true | false

datanucleus.jtaLocator
Description	Selects the locator to use when using JTA transactions so that DataNucleus can find the JTA TransactionManager. If this isn't specified and using JTA transactions DataNucleus will search all available locators which could have a performance impact. See JTA Locator extension. If specifying "custom_jndi" please also specify "datanucleus.jtaJndiLocation"
Range of Values	jboss | jonas | jotm | oc4j | orion | resin | sap | sun | weblogic | websphere | custom_jndi | alias of a JTA transaction locator

datanucleus.jtaJndiLocation
Description	Name of a JNDI location to find the JTA transaction manager from (when using JTA transactions). This is for the case where you know where it is located. If not used DataNucleus will try certain well-known locations
Range of Values	JNDI location

datanucleus.datastoreTransactionDelayOperations
Description	Allows you to turn on/off the delay of datastore operations (persist, update, delete) until flush()/commit(). If using optimistic transactions this will default to true and if using pessimistic transactions will default to false
Range of values	true | false

datanucleus.datastoreTransactionFlushLimit
Description	For use when using datastore transactions and is the limit on number of dirty objects before a flush to the datastore will be performed.
Range of values	1 | positive integer

datanucleus.connectionPoolingType
Description	This property allows you to utilise a 3rd party software package for enabling connection pooling. When using RDBMS you can select from DBCP, C3P0, Proxool, BoneCP, or "dbcp-builtin". You must have the 3rd party jars in the CLASSPATH to use these options. Please refer to the RDBMS Connection Pooling guide for details. Other datastores may offer other options.
Range of Values	None | DBCP | C3P0 | Proxool | BoneCP | "dbcp-builtin" | {others}

datanucleus.connectionPoolingType.nontx
Description	This property allows you to utilise a 3rd party software package for enabling connection pooling for nontransactional connections using a DataNucleus plugin. If you don't specify this value but do define the above value then that is taken by default. Refer to the above property for more details.
Range of Values	None | DBCP | C3P0 | Proxool | BoneCP | "dbcp-builtin" | {others}

datanucleus.connection.nontx.releaseAfterUse
Description	Applies only to non-transactional connections and refers to whether to re-use (pool) the connection internally for later use. The default behaviour is to close any such non-transactional connection after use. If doing significant non-transactional processing in your application then this may provide performance benefits, but be careful about the number of connections being held open (if one is held open per PM/EM).
Range of Values	true | false

datanucleus.connection.resourceType
Description	Resource Type for connection ???
Range of Values	JTA | RESOURCE_LOCAL

datanucleus.connection.resourceType2
Description	Resource Type for connection 2
Range of Values	JTA | RESOURCE_LOCAL

Caching

datanucleus.cache.collections
Description	SCO collections can be used in 2 modes in DataNucleus. You can allow DataNucleus to cache the collections contents, or you can tell DataNucleus to access the datastore for every access of the SCO collection. The default is to use the cached collection.
Range of Values	true | false

datanucleus.cache.collections.lazy
Description	When using cached collections/maps, the elements/keys/values can be loaded when the object is initialised, or can be loaded when accessed (lazy loading). The default is to use lazy loading when the field is not in the current fetch group, and to not use lazy loading when the field is in the current fetch group.
Range of Values	true | false

datanucleus.cache.level1.type
Description	Name of the type of Level 1 cache to use. Defines the backing map. See also Cache docs for JDO, and for JPA
Range of Values	soft | weak | strong | {your-plugin-name}

datanucleus.cache.level2.type
Description	Name of the type of Level 2 Cache to use. Can be used to interface with external caching products. Use "none" to turn off L2 caching. See also Cache docs for JDO, and for JPA
Range of Values	none | soft | weak | coherence | ehcache | ehcacheclassbased | oscache | swarmcache | javax.cache | memcache | {your-plugin-name}

datanucleus.cache.level2.cacheName
Description	Name of the cache. This is for use with plugins such as the Tangosol cache plugin for accessing the particular cache. Please refer to the Cache Guide for JDO or JPA
Range of Values	your cache name

datanucleus.cache.level2.maxSize
Description	Max size for the L2 cache (supported by weak, soft, coherence, ehcache, ehcacheclassbased, javax.cache)
Range of Values	-1 | integer value

datanucleus.cache.level2.clearAtClose
Description	Whether the close of the L2 cache (when the PMF/EMF closes) should also clear out any objects from the underlying cache mechanism. By default it will clear objects out but if the user has configured an external cache product and wants to share objects across multiple PMF/EMFs then this can be set to false.
Range of Values	true | false

datanucleus.cache.queryCompilation.type
Description	Type of cache to use for caching of generic query compilations
Range of Values	none | soft | weak | strong | {your-plugin-name}

datanucleus.cache.queryCompilationDatastore.type
Description	Type of cache to use for caching of datastore query compilations
Range of Values	none | soft | weak | strong | {your-plugin-name}

datanucleus.cache.queryResults.type
Description	Type of cache to use for caching query results.
Range of Values	none | soft | weak | strong | javax.cache | memcache | {your-plugin-name}

datanucleus.cache.queryResults.cacheName
Description	Name of cache for caching the query results.
Range of Values	datanucleus-query | {your-name}

datanucleus.cache.queryResults.maxSize
Description	Max size for the query results cache (supported by weak, soft, strong)
Range of Values	-1 | integer value

Value Generation

datanucleus.valuegeneration.transactionAttribute
Description	Whether to use the PM connection or open a new connection. Only used by value generators that require a connection to the datastore.
Range of Values	New | UsePM

datanucleus.valuegeneration.transactionIsolation
Description	Select the default transaction isolation level for identity generation. Must have datanucleus.valuegeneration.transactionAttribute set to New Some databases do not support all isolation levels, refer to your database documentation. Please refer to the transaction guides for JDO and JPA
Range of Values	read-uncommitted | read-committed | repeatable-read | serializable

datanucleus.valuegeneration.sequence.allocationSize
Description	If using JDO3.0 still and not specifying the size of your sequence, this acts as the default allocation size.
Range of Values	10 | (integer value)

datanucleus.valuegeneration.increment.allocationSize
Description	Sets the default allocation size for any "increment" value strategy. You can configure each member strategy individually but they fall back to this value if not set
Range of Values	10 | (integer value)

MetaData

datanucleus.metadata.jdoFileExtension
Description	Suffix for JDO MetaData files. Provides the ability to override the default suffix and also to have one PMF with one suffix and another with a different suffix, hence allowing differing persistence of the same classes using different PMF's.
Range of values	jdo | {file suffix}

datanucleus.metadata.ormFileExtension
Description	Suffix for ORM MetaData files. Provides the ability to override the default suffix and also to have one PMF with one suffix and another with a different suffix, hence allowing differing persistence of the same classes using different PMF's.
Range of values	orm | {file suffix}

datanucleus.metadata.jdoqueryFileExtension
Description	Suffix for JDO Query MetaData files. Provides the ability to override the default suffix and also to have one PMF with one suffix and another with a different suffix, hence allowing differing persistence of the same classes using different PMF's.
Range of values	jdoquery | {file suffix}

datanucleus.metadata.validate
Description	Whether to validate the MetaData file(s) for XML correctness (against the DTD) when parsing
Range of values	true | false

datanucleus.metadata.autoregistration
Description	Whether to use the JDO auto-registration of metadata. Turned on by default
Range of values	true | false

datanucleus.metadata.supportORM
Description	Whether to support "orm" mapping files. By default we use what the datastore plugin supports. This can be used to turn it off when the datastore supports it but we dont plan on using it (for performance)
Range of values	true | false

Auto-Start

datanucleus.autoStartMechanism
Description	How to initialise DataNucleus at startup. This allows DataNucleus to read in from some source the classes that it was persisting for this data store the previous time. "XML" stores the information in an XML file for this purpose. "SchemaTable" (only for RDBMS) stores a table in the RDBMS for this purpose. "Classes" looks at the property datanucleus.autoStartClassNames for a list of classes. "MetaData" looks at the property datanucleus.autoStartMetaDataFiles for a list of metadata files The other option is "None" (start from scratch each time). Please refer to the Auto-Start Mechanism Guide for more details. The default is "None".
Range of Values	None | XML | Classes | MetaData | SchemaTable

datanucleus.autoStartMechanismMode
Description	The mode of operation of the auto start mode. Currently there are 3 values. "Quiet" means that at startup if any errors are encountered, they are fixed quietly. "Ignored" means that at startup if any errors are encountered they are just ignored. "Checked" means that at startup if any errors are encountered they are thrown as exceptions.
Range of values	Checked | Ignored | Quiet

datanucleus.autoStartMechanismXmlFile
Description	Filename used for the XML file for AutoStart when using "XML" Auto-Start Mechanism

datanucleus.autoStartClassNames
Description	This property specifies a list of classes (comma-separated) that are loaded at startup when using the "Classes" Auto-Start Mechanism.

datanucleus.autoStartMetaDataFiles
Description	This property specifies a list of metadata files (comma-separated) that are loaded at startup when using the "MetaData" Auto-Start Mechanism.

Query control

datanucleus.query.flushBeforeExecution
Description	This property can enforce a flush to the datastore of any outstanding changes just before executing all queries. If using optimistic transactions any updates are typically held back until flush/commit and so the query would otherwise not take them into account.
Range of Values	true | false

datanucleus.query.useFetchPlan
Description	Whether to use the FetchPlan when executing a JDOQL query. The default is to use it which means that the relevant fields of the object will be retrieved. This allows the option of just retrieving the identity columns.
Range of Values	true | false

datanucleus.query.compileOptimised
Description	The generic query compilation process has a simple "optimiser" to try to iron out potential problems in users queries. It isn't very advanced yet, but currently will detect and try to fix a query clause like "var == this" (which is pointless). This will be extended in the future to handle other common situations
Range of Values	true | false

datanucleus.query.jdoql.allowAll
Description	javax.jdo.query.JDOQL queries are allowed by JDO only to run SELECT queries. This extension permits to bypass this limitation so that DataNucleus extension bulk "update" and bulk "delete" can be run.
Range of Values	false | true

datanucleus.query.sql.allowAll
Description	javax.jdo.query.SQL queries are allowed by JDO2 only to run SELECT queries. This extension permits to bypass this limitation (so for example can execute stored procedures).
Range of Values	false | true

datanucleus.query.checkUnusedParameters
Description	Whether to check for unused input parameters and throw an exception if found. The JDO and JPA specs require this check and is a good guide to having misnamed a parameter name in the query for example.
Range of Values	true | false