messages_en.properties

derby database source code.good for you.

42621=A check constraint or generated column that is defined with ''{0}'' is invalid.
42734=Name ''{0}'' specified in context ''{1}'' is not unique.
# DB2 error for invalid set schema
42802=The number of values assigned is not the same as the number of specified or implied columns.
42815.S.713=The replacement value for ''{0}'' is invalid.
42815.S.171=The data type, length or value of arguments ''{0}'' and ''{1}'' is incompatible.
42820=The floating point literal ''{0}'' contains more than 30 characters.
42824=An operand of LIKE is not a string, or the first operand is not a column.
42831=''{0}'' cannot be a column of a primary key or unique key because it can contain null values.
42834=SET NULL cannot be specified because FOREIGN KEY ''{0}''  cannot contain null values.  
42884=No authorized routine named ''{0}'' of type ''{1}'' having compatible arguments was found.
42886=''{0}'' parameter ''{1}'' requires a parameter marker ''?''.
42894=DEFAULT value or IDENTITY attribute value is not valid for column ''{0}''.
428C1=Only one identity column is allowed in a table.
42903=Invalid use of an aggregate function.
42908=The CREATE VIEW statement does not include a column list.
42915=Foreign  Key ''{0}'' is invalid because ''{1}''. 
42916=Synonym ''{0}'' cannot be created for ''{1}'' as it would result in a circular synonym chain.
42972=An ON clause associated with a JOIN operator is not valid.
42X01=Syntax error: {0}.
42X02={0}.
42X03=Column name ''{0}'' is in more than one table in the FROM list.
42X04=Column ''{0}'' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE  statement then ''{0}'' is not a column in the target table.
42X05=Table ''{0}'' does not exist.
42X06=Too many result columns specified for table ''{0}''.
42X07=Null is only allowed in a VALUES clause within an INSERT statement.
42X08=The constructor for class ''{0}'' cannot be used as an external virtual table because the class does not implement ''{1}''. 
42X09=The table or alias name ''{0}'' is used more than once in the FROM list.
42X10=''{0}'' is not an exposed table name in the scope in which it appears.
42622=The name ''{0}'' is too long. The maximum length is ''{1}''.
42X12=Column name ''{0}'' appears more than once in the CREATE TABLE statement.  
54011=Too many columns ({0}) were specified for  table or view {1}. The limit is {2}.
42Z9F=Too many indexes ({0}) on the table {1}. The limit is {2}.  
42X13=Column name ''{0}'' appears more than once times in the column list of an INSERT statement. 
42X14=''{0}'' is not a column in table or VTI ''{1}''.
42X15=Column name ''{0}'' appears in a statement without a FROM list.
42X16=Column name ''{0}'' appears multiple times in the SET clause of an UPDATE statement.
42X17=In the Properties list of a FROM clause, the value ''{0}'' is not valid as a joinOrder specification. Only the values FIXED and UNFIXED are valid.  
42803=An expression containing the column ''{0}'' appears in the SELECT list and is not part of a GROUP BY clause.
42818=Comparisons between ''{0}'' and ''{1}'' are not supported.
42X19=The WHERE or HAVING clause or CHECK CONSTRAINT definition is a ''{0}'' expression.  It must be a BOOLEAN expression.
42X23=Cursor {0} is not updatable.
#42X24=The unary ''-'' operator is not allowed on the ''{0}'' type.
42X25=The ''{0}'' function is not allowed on the ''{1}'' type.
42X26=The class ''{0}'' for column ''{1}'' does not exist or is inaccessible. This can happen if the class is not public.
42X28=Delete table ''{0}'' is not target of cursor ''{1}''.
42X29=Update table ''{0}'' is not the target of cursor ''{1}''.
42X30=Cursor ''{0}'' not found. Verify that autocommit is OFF.
42X31=Column ''{0}'' is not in the FOR UPDATE list of cursor ''{1}''.
42X42=Correlation name not allowed for column ''{0}'' because it is part of the FOR UPDATE list.
42X32=The number of columns in the derived column list must match the number of columns in table ''{0}''.
42X33=The derived column list contains a duplicate column name ''{0}''.
42X34=There is a ? parameter in the select list.  This is not allowed.
42X35=It is not allowed for both operands of ''{0}'' to be ? parameters.
42X36=The ''{0}'' operator is not allowed to take a ? parameter as an operand.
42X37=The unary ''{0}'' operator is not allowed on the ''{1}'' type.
42X38=''SELECT *'' only allowed in EXISTS and NOT EXISTS subqueries.
42X39=Subquery is only allowed to return a single column.
42X40=A NOT statement has an operand that is not boolean . The operand of NOT must evaluate to TRUE, FALSE, or UNKNOWN. 
42X41=In the Properties clause of a FROM list, the property ''{0}'' is not valid (the property was being set to ''{1}''). 
42821=Columns of type ''{0}'' cannot hold values of type ''{1}''. 
42X43=The ResultSetMetaData returned for the class/object ''{0}'' was null. In order to use this class as an external virtual table, the ResultSetMetaData cannot be null. 
42X44=Invalid length ''{0}'' in column specification.
42X45={0} is an invalid type for argument number {1} of {2}.
# 42X46=
# 42X47=
42X48=Value ''{1}'' is not a valid precision for {0}.
42X49=Value ''{0}'' is not a valid integer literal.
42X50=No method was found that matched the method call {0}.{1}({2}), tried all combinations of object and primitive types and any possible type conversion for any  parameters the method call may have. The method might exist but it is not public and/or static, or the parameter types are not method invocation convertible.
42X51=The class ''{0}'' does not exist or is inaccessible. This can happen if the class is not public.
42X52=Calling  method (''{0}'') using a receiver of the Java primitive type ''{1}" is not allowed.
42X53=The LIKE predicate can only have ''CHAR'' or ''VARCHAR'' operands. Type ''{0}'' is not permitted.
42X54=The Java method ''{0}'' has a ? as a receiver.  This is not allowed.
42X55=Table name ''{1}'' should be the same as ''{0}''.
42X56=The number of columns in the view column list does not match the number of columns in the underlying query expression in the view definition for ''{0}''.
42X57=The getColumnCount() for external virtual table ''{0}'' returned an invalid value ''{1}''.  Valid values are greater than or equal to 1. 
42X58=The number of columns on the left and right sides of the {0} must be the same.
42X59=The number of columns in each VALUES constructor must be the same.
42X60=Invalid value ''{0}'' for insertMode property specified for table ''{1}''.
42X61=Types ''{0}'' and ''{1}'' are not {2} compatible.
42X62=''{0}'' is not allowed in the ''{1}'' schema.
42X63=The USING clause did not return any results. No parameters can be set. 
42X64=In the Properties list, the invalid value ''{0}'' was specified for the useStatistics property. The only valid values are TRUE or FALSE. 
42X65=Index ''{0}'' does not exist.
42X66=Column name ''{0}'' appears more than once in the CREATE INDEX statement.
42X68=No field ''{0}'' was found belonging to class ''{1}''.  It may be that the field exists, but it is not public, or that the class does not exist or is not public.
42X69=It is not allowed to reference a field (''{0}'') using a referencing expresssion of the Java primitive type ''{1}''.
42X72=No static field ''{0}'' was found belonging to class ''{1}''.  The field might exist, but it is not public and/or static, or the class does not exist or the class is not public.  
42X73=Method resolution for signature {0}.{1}({2}) was ambiguous. (No single maximally specific method.)
42X74=Invalid CALL statement syntax.
42X75=No constructor was found with the signature {0}({1}).  It may be that the parameter types are not method invocation convertible.
42X76=At least one column, ''{0}'', in the primary key being added is nullable. All columns in a primary key must be non-nullable.
42X77=Column position ''{0}'' is out of range for the query expression.
42X78=Column ''{0}'' is not in the result of the query expression.
42X79=Column name ''{0}'' appears more than once in the result of the query expression.
42877=A qualified column name ''{0}'' is not allowed in the ORDER BY clause.
42X80=VALUES clause must contain at least one element. Empty elements are not allowed. 
42X82=The USING clause returned more than one row. Only single-row ResultSets are permissible.
42X83=The constraints on column ''{0}'' require that it be both nullable and not nullable.
42X84=Index ''{0}'' was created to enforce constraint ''{1}''.  It can only be dropped by dropping the constraint.
42X85=Constraint ''{0}''is required to be in the same schema as table ''{1}''.
42X86=ALTER TABLE failed. There is no constraint ''{0}'' on table ''{1}''. 
42X87=At least one result expression (THEN or ELSE) of the ''{0}'' expression must not be a ''?''. 
42X88=A conditional has a non-Boolean operand. The operand of a conditional must evaluate to TRUE, FALSE, or UNKNOWN.  
42X89=Types ''{0}'' and ''{1}'' are not type compatible. Neither type is assignable to the other type.  
42X90=More than one primary key constraint specified for table ''{0}''.
42X91=Constraint name ''{0}'' appears more than once in the CREATE TABLE statement. 
42X92=Column name ''{0}'' appears more than once in a constraint''s column list.
42X93=Table ''{0}'' contains a constraint definition with column ''{1}'' which is not in the table.
42Z93=Constraints ''{0}'' and ''{1}'' have the same set of columns, which is not allowed. 
42Z9B=The external virtual table interface does not support BLOB or CLOB columns. ''{0}'' column ''{1}''. 
42Z9D=''{0}'' statements are not allowed in ''{1}'' triggers.
42Z9E=Constraint ''{0}'' is not a {1} constraint.
42X94={0} ''{1}'' does not exist.
42X96=The database class path contains an unknown jar file ''{0}''.
42X98=Parameters are not allowed in a VIEW definition.
42Y00=Class ''{0}'' does not implement org.apache.derby.iapi.db.AggregateDefinition and thus cannot be used as an aggregate expression.
42Y01=Constraint ''{0}'' is invalid.
42Y03=''{0}'' is not recognized as a function or procedure.

# EXTERNAL NAME is SQL keyword - do not translate
42Y04=Cannot create a procedure or function with EXTERNAL NAME ''{0}'' because it is not a list separated by periods. The expected format is <full java path>.<method name>.

42Y05=There is no Foreign Key named ''{0}''.
42Y07=Schema ''{0}'' does not exist
42Y08=Foreign key constraints are not allowed on system tables.
42Y09=Void methods are only allowed within a CALL statement.
42Y10=A table constructor that is not in an INSERT statement has all ? parameters in one of its columns.  For each column, at least one of the rows must have a non-parameter.
42Y11=A join specification is required with the ''{0}'' clause.
42Y12=The ON clause of a JOIN is a ''{0}'' expression.  It must be a BOOLEAN expression.
42Y13=Column name ''{0}'' appears more than once in the CREATE VIEW statement.
42Z97=Renaming column ''{0}'' will cause check constraint ''{1}'' to break.
42Z99=String or Hex literal cannot exceed 64K.
42Y16=No public static method ''{0}'' was found in class ''{1}''. The method might exist, but it is not public, or it is not static. 
42846=Cannot convert types ''{0}'' to ''{1}''.
42Y19=''{0}'' appears multiple times in the GROUP BY list. Columns in the GROUP BY list must be unambiguous.
42Y22=Aggregate {0} cannot operate on type {1}.
42Y23=Incorrect JDBC type info returned for column {0}.
42Y24=View ''{0}'' is not updatable. (Views are currently not updatable.) 
42Y25=''{0}'' is a system table.  Users are not allowed to modify the contents of this table.
#42Y26=Parameters are not allowed in the WHEN clause of a trigger.
42Y27=Parameters are not allowed in the trigger action.
42Y29=The SELECT list of a non-grouped query contains at least one invalid expression. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.
42Y30=The SELECT list of a grouped query contains at least one invalid expression. If a SELECT list has a GROUP BY, the list may only contain grouping columns and valid aggregate expressions.  
42Y32=Aggregator class ''{0}'' for aggregate ''{1}'' on type {2} does not implement com.ibm.db2j.aggregates.Aggregator. 
42Y33=Aggregate {0} contains one or more aggregates.
42Y34=Column name ''{0}'' matches more than one result column in table ''{1}''.
42Y35=Column reference ''{0}'' is invalid. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.  
42Y36=Column reference ''{0}'' is invalid.  For a SELECT list with a GROUP BY, the list may only contain grouping columns and valid aggregate expressions.  
42Y37=''{0}'' is a Java primitive and cannot be used with this operator.
42Y38=insertMode = replace is not permitted on an insert where the target table, ''{0}'', is referenced in the SELECT.
# NOTE: The parameter to this message is a keyword used as a noun phrase.
# Some possible values are "subquery", "CurrentDate", and "?".
42Y39=''{0}'' may not appear in a CHECK CONSTRAINT definition because it may return non-deterministic results.
42Y40=''{0}'' appears multiple times in the UPDATE OF column list for trigger ''{1}''.
42Y41=''{0}'' cannot be directly invoked via EXECUTE STATEMENT because it is part of a trigger.
42Y42=Scale ''{1}'' is not a valid scale for a {0}.
42Y43=Scale ''{0}'' is not a valid scale with precision of ''{1}''.
42Y44=Invalid key ''{0}'' specified in the Properties list of a FROM list. The case-sensitive keys that are currently supported are ''{1}''. 
42Y45=VTI ''{0}'' cannot be bound because it is a special trigger VTI and this statement is not part of a trigger action or WHEN clause.
42Y46=Invalid Properties list in FROM list.  There is no index ''{0}'' on table ''{1}''.
42Y48=Invalid Properties list in FROM list.  Either there is no named constraint ''{0}'' on table ''{1}'' or the constraint does not have a backing index.
42Y49=Multiple values specified for property key ''{0}''. 
42Y50=Properties list for table ''{0}'' may contain values for index or for constraint but not both.
42Y55=''{0}'' cannot be performed on ''{1}'' because it does not exist.
42Y56=Invalid join strategy ''{0}'' specified in Properties list on table ''{1}''. The currently supported values for a join strategy are: ''hash'' and ''nestedloop''.
42Y58=NumberFormatException occurred when converting value ''{0}'' for optimizer override ''{1}''.
42Y59=Invalid value, ''{0}'', specified for hashInitialCapacity override. Value must be greater than 0.
42Y60=Invalid value, ''{0}'', specified for hashLoadFactor override. Value must be greater than 0.0 and less than or equal to 1.0.
42Y61=Invalid value, ''{0}'', specified for hashMaxCapacity override. Value must be greater than 0.
42Y62=''{0}'' is not allowed on ''{1}'' because it is a view.
42Y63=Hash join requires an optimizable equijoin predicate on a column in the selected index or heap.  An optimizable equijoin predicate does not exist on any column in table or index ''{0}''. Use the ''index'' optimizer override to specify such an index or the heap on table ''{1}''.
42Y64=bulkFetch value of ''{0}'' is invalid. The minimum value for bulkFetch is 1.
42Y65=bulkFetch is not permitted on ''{0}'' joins.
42Y66=bulkFetch is not permitted on updatable cursors. 
42Y67=Schema ''{0}'' cannot be dropped.
42Y69=No valid execution plan was found for this statement. This may have one of two causes: either you specified a hash join strategy when hash join is not allowed (no optimizable equijoin) or you are attempting to join two external virtual tables, each of which references the other, and so the statement cannot be evaluated.  
42Y70=The user specified an illegal join order. This could be caused by a join column from an inner table being passed as a parameter to an external virtual table.
42Y71=System function or procedure ''{0}'' cannot be dropped.
42Y82=System generated stored prepared statement ''{0}'' that cannot be dropped using DROP STATEMENT. It is part of a trigger. 
42Y83=An untyped null is not permitted as an argument to aggregate {0}.  Please cast the null to a suitable type.
# NOTE: The parameter to this message is a keyword used as a noun phrase.
# Some possible values are "subquery", "CurrentDate", and "?".
42Y84=''{0}'' may not appear in a DEFAULT definition.
42Y85=The DEFAULT keyword is only allowed in a VALUES clause when the VALUES clause appears within an INSERT statement.
42Y90=FOR UPDATE is not permitted in this type of statement.  
42Y91=The USING clause is not permitted in an EXECUTE STATEMENT for a trigger action.
42Y92={0} triggers may only reference {1} transition variables/tables.
42Y93=Illegal REFERENCING clause: only one name is permitted for each type of transition variable/table.
42Y94=An AND or OR has a non-boolean operand. The operands of AND and OR must evaluate to TRUE, FALSE, or UNKNOWN.  
42Y95=The ''{0}'' operator with a left operand type of ''{1}'' and a right operand type of ''{2}'' is not supported.
42Y96.U=UNKNOWN
42Y97=Invalid escape character at line ''{0}'', column ''{1}''.
42Y98.U=Encountered "{0}" at line {1}, column {2}
42Y99.U=Lexical error at line {0}, column {1}. Encountered: {2}
42Z00.U=Java method call or field reference
# This message is put into message 42X75 when a parameter doesn't have a
# datatype. For example, from the parameterWidening test:
#
# values (java.lang.Integer::toString(?, null));
# ERROR 42X50: No method was found with the signature