Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
################################################################################
# Copyright (c) 2003 Andy Jefferson and others. All rights reserved.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Contributors:
# ...
#
# Resources for org.datanucleus.store.rdbms package
################################################################################
#
# Schema Mapping, columns etc
#
020000=Persistent class "{0}" has no table in the database, but the operation requires it. Please check the specification of the MetaData for this class.
020001=Field has no corresponding database column : {0}
020002=Field "{0}" is an indexed List yet is also an M-N relation - this is not supported since it would need an index for both sides of the relation. Either make it the field a Set, or use an ordered List.
020003=Columns "{0} " have been defined with {1} columns, yet there are only {2} to map to!
020004=Columns "{0}" has a column "{1}" which has been defined to map to column "{2}" but this doesn't exist!
020005=Columns "{0}" column number {1} has no remaining columns to map to!
020006=Columns "{0}" has a column "{1}" that has been mapped twice!
020007=Duplicate column name "{0}" defined for table "{1}". You cannot map multiple fields to the same column. The duplicated columns are specified by {2} and {3}. See also persistence property "datanucleus.rdbms.allowColumnReuse"
020008=? datastore-identity|index columns|other non mapped to any field ?
020009=Incompatible data type for column {0} : was {1} (datastore), but type expected was {2} (metadata). Please check that the type in the datastore and the type specified in the MetaData are consistent.
020010=Required columns missing from table "{0}" : {1}. Perhaps your MetaData is incorrect, or you haven't enabled "datanucleus.autoCreateColumns".
020011=Required table missing : "{2}" in Catalog "{0}" Schema "{1}". DataNucleus requires this table to perform its persistence operations. Either your MetaData is incorrect, or you need to enable "datanucleus.autoCreateTables"
020012=Table "{0}" is of wrong type {1}. Should be a table
020013=Table "{0}" is of wrong type {1}. Should be a view
020014=Cannot define a primary key column in a view : {0}, column={1}
020015=Exceeded maximum of {0} foreign keys for table {1}
020016=Exceeded maximum of {0} index keys for table {1}
020017=Invalid view definition for {0} : {1}
020018=Wrong precision for column {0} : was {1} (according to the JDBC driver) but should be {2} (based on the MetaData definition).
020019=Wrong precision for column {0} : was {1} (according to the JDBC driver) but should be {2} (based on the MetaData definition for field {3}).
020020=Expected primary key for table {0} {1} not found in existing keys {2}
020021=Wrong scale for column {0} : was {1} (according to the JDBC driver) but should be {2} (based on the MetaData definition).
020022=Wrong scale for column {0} : was {1} (according to the JDBC driver) but should be {2} (based on the MetaData definition for field {3}).
020023=Classes backed by views cannot have persistence-capable superclasses : {0}
020024=Unexpected column {0} encountered in table {1} schema {2} catalog {3}
020025=Column {0} should not allow nulls but does. You can prevent nulls by specifying "allows-null" as "false" for the in the MetaData
020183=Column {0} has been specified with precision/scale, yet the column datastore type doesn't allow specification of this
020184=Invalid precision, column = {0}
# This is type info so move to different range!
020191=Data type {0} is not recognized by the JDBC. Validation will be ignored
020192=You have specified the default {0} as {1} but for this datastore this has been changed to {2}. This is likely due to missing quote characters, or the datastore storing things in a different case
#
# Query ResultExpressions
#
021033=Query cannot create object of type "{0}" since specified constructor "{1}" doesn't exist
021051="HAVING" expression "{0}" is not a valid boolean expression
021062=Query has reference to member "{0}" of class "{1}" yet this doesnt exist!
021074=The expression {0} is not supported in results.
021118=Query has parameter "{0}" declared as "{1}" yet a value of type "{2}" was supplied
021213=Cannot select multi-valued objects in a result clause of a query
#
# Views
#
031004=Validating view : {0}
031005=Class "{0}" has been defined with an identity-type of "{1}". SQL Views cannot be used with this type. You must use "nondurable".
031006=Class "{0}" has been defined with field "{1}" with a persistence-modifier of "{2}". You cannot use this with SQL Views - must be persistent or transactional.
031007=Class "{0}" uses an SQL View, however the method "{1}" has just been called. This is not supported for SQL Views.
031008=Class "{0}" uses an SQL View consequently DataNucleus doesnt support the generation of new identities for objects of this type.
031009=Class "{0}" uses an SQL View, however you are not allowed to use macros (such as "{1}") in the view definition.
#
# Mapping
#
041000=The Java type {0} has no known mapping class available in DataNucleus.
041001=The field "{0}" with Java type {1} has no known mapping class available in DataNucleus.
041004=Somehow {0}.{1}() was called, which should have been impossible!
041005=Somehow {0}.{1}() was called on the mapping for field="{2}", which should have been impossible!
041006=Constructor ({0},{1}) not found for Mapping type {2}
041007=Constructor ({0},{1},{2}) not found for Mapping type {3}
041008=Constructor ({0},{1},{2},{3}) not found for Mapping type {4}
041009=Failed to generate new Mapping of type {0}, exception : {1}
041010=Failed to generate new Mapping of type {0} for table {1}, field {2}, exception : {3}
041011=Missing constructor {0}(ClassTable, int)
041012={0} can only be used with a persistence-capable field
041013=The plugin.xml has specified a datastore-mapping class of "{0}" yet this is not found
041014=Field "{0}" has been specified to use a mapping class "{1}" yet this class was not found! Please check your metadata and respecify the mapping class.
041015=Cannot assign field to an object from a different PersistenceManager
041016=Object is not a PersistenceCapable instance. Object class = {0}, value = {1}
041018=Object "{0}" has field "{1}" with a 1-1 bidirectional relation set to relate to "{2}" but this object hasnt had the relation at field "{3}" set so updating the object directly.
041019=Object "{0}" has bidirectional field "{1}" currently set to "{2}" but this object is being deleted so nulling this field
041020=Object "{0}" has field "{1}" with a 1-1 bidirectional relation set to relate to "{2}" but this object relates back to a different object "{3}"!
041022=Object "{0}" has field "{1}" with an N-1 bidirectional relation set to relate to "{2}" but the collection at "{3}" doesn't contain this object.
041023=Specified field "{0}" has no container (collection/map/array) MetaData!
041034=Retrieved object with OID "{0}"
041038=Primary Key column "{0}" for table "{1}" is not mapped.
041042=Field "{0}" is specified as embedded. DataNucleus doesnt currently support the persistence of embedded Object fields.
041044=Field "{0}" is a reference field (interface/Object) of type {1} but DataNucleus is unable to assign an object of type "{2}" to this field. You can only assign this field to a type specified by the "implementation-classes" extension attribute.
041050=Failure in call to "{0}" for position {1} for column "{2}" : {3}
#
#
045000=Execution Time = {0} ms
045001=Execution Time = {0} ms (number of rows = {1}) on PreparedStatement "{2}"
#
# DataSource
#
047000=The specified datastore driver ("{0}") was not found in the CLASSPATH. Please check your CLASSPATH specification, and the name of the driver.
047001=You have specified to use a "{0}" connection pool yet one of the required libraries for this ({1}) was not found.
047002=Error creating database connection pool of type "{0}" for driver "{1}" and URL "{2}" : {3}
047003=The connection pool plugin of type "{0}" was not found in the CLASSPATH!
047004=Attempt to invoke the "{0}" plugin to create a ConnectionPool gave an error : {1}
047005=Error reading the configuration file for the connection pool : {0}. Check that it is accessible in the CLASSPATH
047006=Invalid datastore driver class "{0}" : maybe you haven't specified the JDBC driver JAR in your CLASSPATH, or the name of the class is incorrect.
047007=No datastore driver class has been specified!
047008=Created {0} data source using pooling type of {1}
047009=Unable to create {0} datasource for connections due to invalid/insufficient input. Consult the log for details and/or review the settings of "datastore.connectionXXX" properties
047010=Closing Connection Pool {0}
#
# Exceptions
#
048000= Exception : {0}
#
# SchemaAutoStarter
#
049000=Failed to retrieve classes from SchemaTable : {0}
049001=Failed to validate SchemaTable for Schema "{0}". Either it doesn't exist, or doesn't validate : {1}
049002=Dropping Schema Table "{0}" and recreating as new
049003=Error adding class {0} to list of persistence-managed classes : {1}
049004=Deleting class {0} from list of persistence-managed classes
049005=Error deleting class {0} from list of persistence-managed classes : {1}
049006=Error deleting all persistence-managed classes from supported list : {1}
049007=Class names and associated table names are stored in the datastore in a table "{0}"
049008=Unable to use the SchemaAutoStarter since it is not open!
049009=Unable to open the SchemaAutoStarter since it is already open!
049010=Unknown error in datastore : {0}
#
# RDBMS Manager
#
050000=Unable to set the ConnectionProvider to be "{0}" since no plugin exists for that value. Please check your setting and your CLASSPATH
050001=Unable to create a ConnectionProvider of name "{0}" : "{1}"
050002=Default Catalog name "{0}" has been specified yet the Database Adapter (JDBC driver) doesn't support specification of catalog name in table definitions !
050003=Default Schema name "{0}" has been specified yet the Database Adapter (JDBC driver) doesn't support specification of schema name in table definitions !
050004=Failed initialising database.
050005=Error obtaining connection to database : {0}
050006=Please check that your database JDBC driver is accessible, and the database URL and username/password are correct.
050007=Could not obtain connection due to unknown reason. Check your database configuration. e.g security/firewall problem?
050012=Schema Data has not been initialised for Catalog "{0}", Schema "{1}"
050013=Class "{0}" has been specified to use an inheritance strategy of "superclass-table", yet the table for a superclass cannot be found!
050014=Class "{0}" has been specified as "embedded-only", and so it can only exist within the tables of other classes. No table will be created.
050015=The class specified ({0}) has a default table name of {1}, but this is in use by a different class ({2}). DataNucleus will use a separate instance of this table internally and data will be persisted to the same datastore table. It is your responsibility to make sure that both of these classes are compatible for saving to the same place.
050016=Join Tables can only be created as a side effect of adding a new class
050017=Persistent Class not found for id "{0}"
050018=Object with id "{0}" not found !
050019=Attempt to find new application-identity for class ({0}) that does not use "application identity".
050020=Attempt to find new application-identity for class {0} yet field {1} has invalid type ({2}). Should be int/long/Integer/Long.
050021=Class {0} has been defined with objectid-class {1}, yet this is already used by a different inheritance tree (e.g by class {2}). Please correct this so that each inheritance tree uses their own objectid-class.
050022=Id {0} is assigned to class {1}, but it's not the correct object-id type for this class.
050023=Obtaining next ID for class {0}
050024=Error while obtaining connection for value generation : {0}
050025=Error while closing connection for value generation : {0}
050028=Loading column info for table(s) "{0}" in Catalog "{1}", Schema "{2}"
050029=Column info loaded for Catalog "{0}", Schema "{1}", {2} tables, time = {3} ms
050030=No column info found for table "{0}" - the table apparently doesnt yet exist in the datastore
050031=No column info found for column "{0}" of table "{1}"
050032=Column info retrieved for table "{0}" : {1} columns found
050033=Column info retrieved for column "{0}" of table "{1}"
050034=Table for class {0} has no ID column
050035=Field {0}.{1} has no table of its own in which to look for {2}
050036=Invalid pseudo-field name {0} in macro {1}, must be "owner", "element" or "index"
050037=Invalid pseudo-field name {0} in macro {1}, must be "owner", "key" or "value"
050038=Add classes to Catalog "{0}", Schema "{1}"
050039=Add classes transaction is not active
050040=An error occurred while auto-creating schema elements - rolling back
050041=An error occurred while auto-creating schema elements. The following exception occurred while attempting to rollback the partially-completed schema changes : {0}
050042=Referenced class/interface {0} is not persistence-capable !
050043=Error(s) were found while auto-creating/validating the datastore for classes. The errors are printed in the log, and are attached to this exception.
050044=An exception was thrown while adding/validating class(es) : {0}
050045=Removing all classes from persistence management for Catalog "{0}", Schema "{1}"
050046=Removing class "{0}" from persistence management
050047=An exception was thrown while dropping class(es) : {0}
050048=Updating table "{0}" for Catalog "{1}", Schema "{2}"
050049=No metadata found for field {0} with non PersistenceCapable elements/values. This metadata {1} needs adding the join.
050050=Field "{0}" is a map that has been specified without a join table and neither the key nor the value has a mapped-by specified. This is invalid!
050051=Invalid query argument {0} : should be a String containing a filter for the query, or an existing Query to use as a basis.
050052=Exception thrown trying to get the server date : {0}
050053=Schema Transaction committing with connection "{0}"
050054=Schema Transaction rolling back with connection "{0}"
050055=Schema Transaction closing with connection "{0}"
050056=Schema Transaction threw exception "{0}"
050057=Schema Transaction started with connection "{0}" with isolation "{1}"
#
# RDBMS Adapter
#
051000=No Database Adapter was found for your JDBC driver specified. Faling back to the generic DatabaseAdapter!
051001=The Datastore Adapter class "{0}" was not found. If this is a class that was specified by you in initialising the PMF, please try the DataNucleus auto-detection instead since your class wasnt found.
051002=The Datastore Adapter class "{0}" for vendor-id "{1}" with priority "{2}" was overridden by class "{3}" with the same priority
051003=The Oracle adapter was not found
051004=Error accessing database MetaData
051005=JDBC type "{0}" not supported by the JDBC driver. Please check your specification of "jdbc-type" and the driver capabilities.
051006=None of the specified JDBC types are supported
051007=SQL type "{0}" (for JDBC type "{1}") was discarded by the database adapter
051008=Transaction Isolation level {0} is unsupported. Not used.
051009={0} can only be used with a persistence-capable field
051010=Missing constructor {0}(ClassBaseTable,int)
051011=Fields of type {0} not (yet) supported
051012=Can't access constructor for mapping object with class {0}
051013=Can't instantiate mapping object with class {0}
051014=Constructor for {0} failed
051015=Don't know how to determine the current catalog name for this type of DBMS : {0} {1}
051016=Don't know how to determine the current schema name for this type of DBMS : {0} {1}
051017=Database adapter allows catalogs to be used in table definitions
051018=Database adapter allows schemas to be used in table definitions
051019=This adapter does not support auto-increment keys
051020=This adapter does not support sequences
051021=This adapter does not support sequences without names
051022=This adapter does not support sequences with max value.
051023=This adapter does not support sequences with cache sizes.
051024=Error : This JDBC driver has no product name. Unable to select the requisite RDBMS adapter.
051025=Error : This JDBC driver gave an error when trying to access the product name. Unable to select the requisite RDBMS adapter : {0}
051026=Error : An error occurred trying to instantiate an instance of the adapter "{0}" for this JDBC driver : {1}
051027=Error initialising derby schema : {0}
051028=Sequences with null name are not supported
#
# Connection
#
052000=Failure to open a connection for datasource "{0}" - check your datasource specification and/or driver
052001=Connection "{0}" opened
052002=Connection "{0}" opened with isolation level "{1}" and auto-commit={2}
052003=Connection "{0}" closed
052004=Connection "{0}" is already closed
052005=Connection "{0}" non enlisted to a transaction is being committed.
052006=Connection "{0}" non enlisted to a transaction is being rolled back.
#
# SQLController
#
052100=Adding statement "{0}" to the current batch (new batch size = {1})
052101=The current batch limit has been reached so processing batched SQL statement "{0}"
052102=The currently being batched SQL statement "{0}" is not yet processable, so unable to batch the requested statement "{1}". Processing as normal
052103=The requested statement "{0}" has been made batchable
052104=Batch has been added to statement "{0}" for processing (batch size = {1})
052106=Connection has a batched statement "{0}" but is not yet processable so leaving it and processing query statement ("{1}")
052108=Exception thrown flushing changes to datastore
052109=Using PreparedStatement "{0}" for connection "{1}"
052110=Closing PreparedStatement "{0}"
#
# Extent
#
053000=Extent cannot be created because the class "{0}" has no persistent fields.
053001=Extent cannot be created because the field mapping "{0}" is unsuitable for a view column, for class "{1}"
053002=Extent cannot be created for "{0}" since it requires the loading of subclass "{1}" and this was not found in the CLASSPATH!.
#
# Request
#
052200=Insert attempted for class "{0}" yet no (application identity) field(s) was provided.
052201=Object with id "{0}" in table {1} has no version set on the object in memory and you want to update it!! Please report this bug to the developers of DataNucleus with a way of reproducing it
052202=Object with id "{0}" in table {1} has no version set on the object in memory and you want to delete it!! Please report this bug to the developers of DataNucleus with a way of reproducing it
052203=Object "{0}" (id="{1}") has been changed in the datastore since your last read. Your transaction is using version "{2}" but this doesnt exist in the datastore now
052204=Object with id "{0}" in table {1} has been deleted from the datastore since your last read.
052205=Object was inserted into the datastore table {0} with an "autoassign"/"identity" column, yet the datastore returns null when asked for the value of the identity. This is a bug in your datastore driver. The workaround is to use an alternative datastore/value strategy for the field.
052206=Object "{0}" was inserted in the datastore and was given strategy value of "{1}"
052207=Object "{0}" being inserted into table "{1}"
052208=Insert of object "{0}" using statement "{1}" failed : {2}
052209=Insert of object "{0}" is calling postInsert for field "{1}"
052210=Object "{0}" being deleted from table "{1}"
052211=Delete of object "{0}" using statement "{1}" failed : {2}
052212=Delete of object "{0}" is calling preDelete for field "{1}"
052213=Delete of object "{0}" is processing field "{1}"
052214=Object "{0}" having fields "{1}" updated in table "{2}"
052215=Update of object "{0}" using statement "{1}" failed : {2}
052216=Update of object "{0}" is calling postUpdate for field "{1}"
052217=Update of object "{0}" is updating field "{1}"
052218=Object "{0}" having fields "{1}" fetched from table "{2}"
052219=Fetch of object "{0}" using statement "{1}" failed : {2}
052220=Search for object "{0}" using statement "{1}" failed : {2}
052221=A fetch request has a main table with primary key with {0} columns, yet the passed field which will join to it has {1} columns! Please report this as a DataNucleus bug!
052222=Insert of object "{0}" is calling insertPostProcessing for field "{1}"
052223=Locate of objects "{0}", performing SELECT on table "{1}"
#
# ResultObjectFactory
#
052300=Query should return an instance of type "{0}" yet this is abstract! Falling back to its next subclass of "{1}". Consider using a discriminator in the table to define the type
052301=Query should return an instance of type "{0}" yet this is abstract! Please check your data and model
#
# FieldManager
#
052400=Field {0} is null, but is mandatory as it's described in the jdo metadata
#
# Query Statement
#
052500=Range variable {0} already in use in query : {1}
052501=Range variable {0} doesn't exist
052502=The query required use of DISTINCT, however it was not possible to use the "FOR UPDATE" lock because the RDBMS doesnt support the use of this syntax in one query
052503=The ordering clause should be passed the same number of ordering expressions and ordering directions but was passed {0} expressions and {1} directions!
052504=The datastore in use doesnt support the necessary syntax required for this operation "{0}".
052505=OracleAdapter only supports boolean char expressions
052510=Query extension 'datanucleus.rdbms.query.resultSetType' has valid values of scroll-sensitive,scroll-insensitive,forward-only only.
052511=Query extension 'datanucleus.rdbms.query.resultSetConcurrency' has valid values of read-only,updateable only.
052512=Query extension 'datanucleus.rdbms.query.fetchDirection' has valid values of forward,reverse,unknown only
052520=Query generation selecting all fields of "{0}" since nondurable identity
#
# SQL Warnings
#
052700=SQL Warning : {0}
052701=Error obtaining warnings from connection {0}
052702=Error obtaining warnings from statement {0}
052703=Error obtaining warnings from result-set {0}
#
# Mappings
#
054000=SQL type {1} declared for field of java type {0} cant be mapped for this datastore.
054001=SQL type {1} declared for field "{2}" of java type {0} cant be mapped for this datastore.
054002=JDBC type {1} declared for field of java type {0} cant be mapped for this datastore.
054003=JDBC type {1} declared for field "{2}" of java type {0} cant be mapped for this datastore.
054004=The java type {0} (jdbc-type="{1}", sql-type="{2}") can't be mapped for this datastore. No mapping is available.
054005=The java type {0} (jdbc-type="{1}", sql-type="{2}") for field "{3}" can't be mapped for this datastore. No mapping is available.
054006=SQL type {1} declared for field {0} cant be mapped for this datastore.
054007=JDBC type {1} declared for field {0} cant be mapped for this datastore.
054008=The java type {1} declared for field {0} can't be mapped for this datastore using the JDBC/SQL type specified. Please either change the JDBC/SQL type specification, or remove it so that the DataNucleus default can be tried.
054009=Adding RDBMS support for Java type {0} (jdbc-type={1}, sql-type={2}, datastore-mapping-type={3}, default={4})
054010=Removing RDBMS support for Java type {0} (jdbc-type={1}, sql-type={2})
054011=SQL type {1} declared for field of java type {0} unknown internally for this datastore, so trying jdbc-type {2}. Mapping is likely non-optimal without specific sql-type support
054012=SQL type {1} declared for field "{2}" of java type {0} unknown internally for this datastore, so trying jdbc-type {3}. Mapping is likely non-optimal without specific sql-type support
055000=No suitable JDBC type found for column "{0}"
055001=Cannot set {0} parameter: value = {1} for column "{2}" : {3}
055002=Cannot get {0} result for param = {1} for column "{2}" : {3}
055003=Illegal null value in column {0}
055004=Illegal value {0} in column {1}
055005=Object of type {0} isn't Serializable
055006=Boolean field stored in "{0}" column had illegal value "{1}" when retrieved from the datastore!
055007=Attempt to store value "{0}" in column "{1}" that has maximum length of {2}. Please correct your data!
055008=Attempt to store a char with unassigned value (0x0) but this database doesnt support storing this value. Using space (' ') instead
#
# Tables
#
057000=Table object has already been initialised : {0}
057001=Table object has not been been initialised : {0}
057002=Table has not been validated : {0}
057003=Attempt to create table for class {0} which has been specified to use an inheritance strategy of "{1}". This means it should not have its own table.
057004=No identity not supported for class {0}
057005=Invalid identity type for class {0}
057006=Invalid persistence-modifier for field {0}
057007=The field "{0}" represents a map with the key stored as a field in the value, yet the field specified ({1}) isnt found in the value class.
057008=The field "{0}" represents a map with the value stored as a field in the key, yet the field specified ({1}) isnt found in the key class.
057009=The field "{0}" represents a map with no join table. In this case you must specify "mapped-by" on either the key or the value element to specify that either the key is stored in the value class, or that the value is stored in the key class.
057010=Field [{0}] -> Column(s) [{1}] using mapping of type "{2}" ({3})
057011=There is no field associated with the column [{0}] using the type "{1}"
057012=More than one map has its "mapped-by" attribute set to field "{0}" (for example field "{1}"). This could cause a problem since objects of this class can, as a result, be part of multiple relationships and so functionality like dependent-field may not work reliably.
057013=Table class={0}, object-class={1}
057014=Class "{0}" has been defined with an array of element "{1}" yet no MetaData is found for this element.
057015=No MetaData found for field {0}
057016=Class "{0}" has been defined with a Collection containing element "{1}" yet no MetaData is found for this element.
057017=No
