db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <da...@vancouvering.com>
Subject Re: [jira] Commented: (DERBY-296) Document
Date Fri, 20 May 2005 00:13:09 GMT
Great, thanks Jeff!

David

Jeff Levitt wrote:

> Here's a text file that might help...it litst all the
> messages with changes, and then the old and the new
> version.
> 
> By the way, I am currently away on vacation, and my
> access to email is limited.  Just wanted to explain
> why you might not get responses from me on various
> items of discussion from time to time.  I may not be
> able to get to topics that people address to me until
> I get back in a few weeks, but I will do my best.
> 
> 
> --- David Van Couvering <david@vancouvering.com>
> wrote:
> 
>>I could do this; every time I talk to customers they
>>hammer into me that 
>>clear and helpful error messages are key.
>>
>>It would *really* help if I knew which message texts
>>were modified in 
>>the doc.  Is it limited to the Derby-specific
>>messages with SQLStates 
>>starting with "X"?
>>
>>Would I submit this as an independent patch to the
>>same JIRA item?  Note 
>>also that I may find "bugs" in the messages that
>>would require a redo of 
>>the documentation...
>>
>>David
>>
>>Jean T. Anderson wrote:
>>
>>>David Van Couvering wrote:
>>>
>>>
>>>>I would agree...  I think the right thing to do
>>
>>would be to fix the code.
>>
>>>>David
>>>
>>>
>>>
>>>is that an offer?  :-)
>>>
>>> -jean
>>>
>>>
>>>
>>>>Jean T. Anderson (JIRA) wrote:
>>>>
>>>>
>>>>>     [ 
>>>>>
>>
> http://issues.apache.org/jira/browse/DERBY-296?page=comments#action_65717
> 
>>>>>]
>>>>>     Jean T. Anderson commented on DERBY-296:
>>>>>----------------------------------------
>>>>>
>>>>>Regarding this:
>>>>>
>>>>>
>>>>>
>>>>>>During my work, I discovered that many of the
>>
>>messages could use 
>>
>>>>>>some spellchecking, grammar checking, etc.
>>
>>Rather than document them 
>>
>>>>>>this way, I corrected them. At some point a
>>
>>separate JIRA issue 
>>
>>>>>>should be made, and someone should undertake
>>
>>the task of fixing the 
>>
>>>>>>actual message strings to reflect the correct
>>
>>grammar, spelling, 
>>
>>>>>>punctuation, etc. used in this document.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>I'm concerned users might be confused if the
>>
>>error message an 
>>
>>>>>application spits out does not exactly match the
>>
>>error message string 
>>
>>>>>documented in the Reference Manual.
>>>>>I think this work shouldn't be committed until
>>
>>doc matches code 
>>
>>>>>(whether it involves changing the messages in
>>
>>this patch or modifying 
>>
>>>>>the code to match these).
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Document
>>>>>>--------
>>>>>>
>>>>>>        Key: DERBY-296
>>>>>>        URL:
>>
>>http://issues.apache.org/jira/browse/DERBY-296
>>
>>>>>>    Project: Derby
>>>>>>       Type: Task
>>>>>> Components: Documentation
>>>>>>Environment: all
>>>>>>   Reporter: Jeff Levitt
>>>>>>   Assignee: Jeff Levitt
>>>>>>   Priority: Minor
>>>>>>Attachments: derby296.zip
>>>>>>
>>>>>>I've spent some time compiling a list of error
>>
>>messages for Derby, 
>>
>>>>>>to expand on the error messages section
>>
>>currently in the Reference 
>>
>>>>>>Manual.  I am about ready to submit a candidate
>>
>>patch, and I am 
>>
>>>>>>opening up a JIRA issue to contain it.
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>------------------------------------------------------------------------
>>
>>Original: 0100E|XX Attepmt to return too many result sets
>>Changed to: XX Attempt to return too many result sets. 
>>
>>Original: 22014|The start positon for LOCATE is invalid; it must be a positive integer.
 The index to start the search from is '{2}'.  The string to search for is '{0}'.  The string
to search from is '{1}'.
>>Changed to: 22014|The start position for LOCATE is invalid; it must be a positive
integer. The index  to start the search from is '{2}'.  The string to search for is
>>'{0}'.  The string to search from is '{1}'. 
>>
>>Original: 22019|Invalid escape sequence, '{0}'. The escape string must be exactly
one character. It can not be a null or more than one character.   
>>Changed to: 22019|Invalid escape sequence, '{0}'. The escape string must be exactly
one character.It cannot be a null or more than one character.
>>
>>Original: 25501|Unable to set the connection read only property in an active transaction.

>>Changed to: 25501|Unable to set the connection read-only property in an active transaction.
>>
>>Original: 40XD1|Container was opened in read only mode    
>>Changed to: 40XD1|Container was opened in read-only mode.   
>>
>>Original: 40XD2|Container {0} cannot be opened, either it has been dropped or is non-existant
>>Changed to: 40XD2| Container {0} cannot be opened; it either has been dropped
>>or does not exist.
>>
>>Original: 40XT4|An attempt was made to close a transaction that was still active,
transaction has been aborted.
>>Changed to: 40XT4|An attempt was made to close a transaction that was still active.
The transaction has been aborted.
>>
>>Original: 40XT6|Database is in quiescent state, cannot activate transaction.  Please
wait for a moment till it exits the quiescent state. 
>>Changed to: 40XT6|Database is inactive and cannot activate the transaction.  Please
wait for
>>a moment until it exits the inactive state. 
>>
>>Original:40001|A lock could not be obtained due to a deadlock, cycle of locks &
waiters is:
>>{0}The selected victim is XID : {1} 
>>Changed to: A lock could not be obtained due to a deadlock, cycle of locks and waiters
>>is: {0} The selected victim is XID :{1}. 
>>
>>Original: 42601|ALTER TABLE statement can not add an IDENTITY column to a table. 

>>Changed to: 42601|ALTER TABLE statement cannot add an IDENTITY column to a table.

>>
>>Original: 42610|All the arguments to the COALESC/VALUE function can not be parameters.
Need to have at least one non-parameter argument.  
>>Changed to: 42610|All the arguments to the COALESC/VALUE function cannot be parameters.
The
>>function needs at least one argument that is not a parameter. 
>>
>>Original: 42X43| The ResultSetMetaData returned for the class/object '{0}' was null.
The ResultSetMetaData must be non-null in order to use this class as an external virtual table.
    
>>Changed to: 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. 
>>
>>Original: 42X57|The getColumnCount() for external virtual table '{0}' returned an
invalid value '{1}'.  Valid values are >= 1. 
>>Changed to: 42X57|The getColumnCount() for external virtual table '{0}' returned an
invalid value '{1}'.  Valid values are greater than or equal to 1. 
>>
>>Original: 42X82|The USING clause returned more than one row, only single row ResultSets
are permissable.  
>>Changed to: 42X82| The USING clause returned more than one row, only single row ResultSets
are
>>permissible.
>>
>>Original: 42Y24|View '{0}' is not updatable. (Views are currently not updateable.)
  
>>Changed to: 42Y24| View '{0}' is not updatable. (Views are currently not updatable.)

>>
>>Original: 42Y35|Column reference '{0}' is invalid. When the SELECT list contains at
least 1 aggregate then all entries must be valid aggregate expressions.     
>>Changed to: 42Y35|Column reference '{0}' is invalid. When the SELECT list contains
at least
>>one aggregate then all entries must be valid aggregate expressions.  
>>
>>Original: 42Y56|Invalid joinStrategy, '{0}', specified in Properties list on table
'{1}'. The currently supported values for joinStrategy are 'hash', 'nestedloop'.  
>>Changed to: 42Y56|Invalid joinStrategy, '{0}', specified in Properties list on table
'{1}'. The currently supported values for joinStrategy are 'hash' and 'nestedloop'.  
>>
>>Original: 42Y59|Invalid value, '{0}', specified for hashInitialCapacity override.
Value must be > 0. 
>>Changed to: 42Y59|Invalid value, '{0}', specified for hashInitialCapacity override.
Value must
>>be greater than 0.                                                               
                                                                                         
                              Original: 42Y60|Invalid value, '{0}', specified for hashLoadFactor
override. Value must be > 0.0 and <= 1.0.
>>Changed to: 42Y60|Invalid value, '{0}', specified for hashLoadFactor override. Value
must be
>>greater than 0.0 and less than or equal to 1.0.
>>
>>Original: 42Y61|Invalid value, '{0}', specified for hashMaxCapacity override. Value
must be > 0.
>>Changed to: 42Y61|Invalid value, '{0}', specified for hashMaxCapacity override. Value
must be
>>greater than 0.
>>
>>Original: 42Y66|bulkFetch is not permitted on updateable cursors.
>>Changed to: 42Y66|bulkFetch is not permitted on updatable cursors. 
>>
>>Original:42Y82|System generated stored prepared statement '{0}' cannot be dropped
using DROP STATEMENT.  It is part of a trigger.
>>Changed to: 42Y82|System generated stored prepared statement '{0}' that cannot be
dropped using
>>DROP STATEMENT. It is part of a trigger. 
>>
>>Original: 42Z19|Column '{0}' is being referenced by atleast one foreign key constraint
'{1}'. To alter the length of this column, you should drop referencing constraints, perform
the ALTER TABLE and then recreate the constraints. 
>>Changed to: 42Z19|Column '{0}' is being referenced by at least one foreign key constraint
'{1}'.
>>To alter the length of this column, you should drop referencing constraints,
>>perform the ALTER TABLE and then recreate the constraints. 
>>
>>Original: 42Z21|Invalid increment specified for identity for column '{0}'. Increment
must be non zero.      
>>Changed to: 42Z21|Invalid increment specified for identity for column '{0}'. Increment
cannot
>>be zero.  
>>
>>Original: 42X04|Column '{0}' is not in any table in the FROM list or it appears within
a join specification and is outside the scope of the join specification or it 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. 
>>
>>Changed to: 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.
>>
>>Original: 42X08|The constructor for class '{0}' cannot be used as an external virtual
table as the class does not implement '{1}' 
>>Changed to: 42X08|The constructor for class '{0}' cannot be used as an external virtual
table because the class does not implement '{1}'. 
>>
>>Original: 42X10|'{0}' is not an exposed table name in the scope in which it appears.
>>Changed to: 42X10|In the scope in which it appears '{0}' is not an exposed table name.
>>
>>Original: 42X12|Column name '{0}' appears more than once in the create table statement.
 
>>Changed to: 42X12|Column name '{0}' appears more than once in the CREATE TABLE statement.
 
>>
>>Original: 42X13|Column name '{0}' appears more than once times in the column list
of an insert statement. 
>>Changed to: 42X13|Column name '{0}' appears more than once times in the column list
of an INSERT statement. 
>>
>>Original: 42X16|Column name '{0}' appears multiple times in the SET clause of an update
statement.
>>Changed to: 42X16|Column name '{0}' appears multiple times in the SET clause of an
UPDATE statement.
>>
>>Original: 42X17|The value '{0}' is not valid as a joinOrder specification in the Properties
list of a FROM clause. Only the values FIXED and UNFIXED are valid.     
>>Changed to: 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.  
>>
>>Original: 42X29|Update table '{0}' is not target of cursor '{1}'.
>>Changed to: 42X29|Update table '{0}' is not the target of cursor '{1}'.
>>
>>Original: 42X31|Column '{0}' is not in the FOR UPDATE list of cursor '{1}'.
>>Changed to: 42X31|Column '{0}' is not in the FOR UPDATE list of cursor '{1}'.
>>
>>Original: 42X40|A NOT has a non-Boolean operand. The operand of NOT must evaluate
to TRUE, FALSE, or UNKNOWN.   
>>Changed to: 42X40|A NOT statement has an operand that is not boolean . The operand
of NOT must
>>evaluate to TRUE, FALSE, or UNKNOWN. 
>>
>>Original:42X41|The property '{0}' is not valid in the Properties clause of a FROM
list (the property was being set to '{1}'). 
>>Changed to:42X41|In the Properties clause of a FROM list, the property '{0}' is not
valid (the
>>property was being set to '{1}'). 
>>
>>Original: 42X50|No method was found to be able to match method call {0}.{1}({2}),
even tried all combinations of object and primitive types and any possible type conversion
for any parameters the method call may have.  It may be that the method exists, but it is
not public and/or static, or that the parameter types are not method invocation convertible.

>>Changed to: 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 mightexist but it is not public and/or static, or the
parameter types are not method invocation convertible.
>>
>>Original: 42X63|The USING clause did not return any results, no parameters can be
set. 
>>changed to: 42X63|The USING clause did not return any results. No parameters can be
set. 
>>
>>Original:42X64|Invalid value '{0}' specified for useStatistics property in the Properties
list. TRUE or FALSE are the only valid values.
>>Changed to: 42X64|In the Properties list, the invalid value '{0}' was specified for
the useStatistics
>>property. The only valid values are TRUE or FALSE. 
>>
>>Original:42X66|Column name '{0}' appears more than once in the create index statement.

>>Changed to: 42x66|Column name '{0}' appears more than once in the CREATE INDEX statement.

>>
>>Original: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.
>>Changed to: No field '{0}' was found belonging to class '{1}'. The field might exist,
but it is not public, or the class does not exist or is not public. 
>>
>>Original: 42X72|No static field '{0}' was found belonging to class '{1}'.  It may
be that the field exists, but it is not public and/or static, or that the class does not exist
or is not public.    
>>Changed to: 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.  
>>
>>Original: 42X80|VALUES clause must contain at least 1 element and all elements must
be non-empty. 
>>Changed to: 42X80|VALUES clause must contain at least one element. Empty elements
are not allowed. 
>>
>>Original:42X82|The USING clause returned more than one row, only single row ResultSets
are permissable. 
>>Changed to:42x82|The USING clause returned more than one row. Only single-row ResultSets
are
>>permissible.
>>
>>Original: 42X83|The constraints on column '{0}' requires that it be both nullable
and not nullable. 
>>Changed to: 42X83|The constraints on column '{0}' require that it be both nullable
and not nullable.
>>
>>Original: 42X86|ALTER table failed. There is no constraint '{0}' on table '{1}'. 
>>Changed to: 42x86|ALTER TABLE failed. There is no constraint '{0}' on table '{1}'.

>>
>>Original: 42X87|At least one result expression (then or else) of the '{0}' expression
must not be a '?'.
>>Changed to: 42X87|At least one result expression (THEN or ELSE) of the '{0}' expression
must
>>not be a '?'. 
>>
>>Original:42X88|A Conditional has a non-boolean operand. The operand of Conditional
must evaluate to TRUE, FALSE, or UNKNOWN.
>>Changed to: 42X88|A conditional has a non-Boolean operand. The operand of a conditional
must
>>evaluate to TRUE, FALSE, or UNKNOWN.  
>>
>>Original:42X89|Types '{0}' and '{1}' are not type compatible. (Neither type is assignable
to the other type.) 
>>Changed to:42X89|Types '{0}' and '{1}' are not type compatible. Neither type is assignable
>>to the other type.  
>>
>>Original:42X90|More than 1 primary key constraint specified for table '{0}'.
>>Changed to: 42X90|More than one primary key constraint specified for table '{0}'.
>>
>>Original: 42X91|Constraint name '{0}' appears more than once in the create table statement.
 
>>Changed to: 42X91|Constraint name '{0}' appears more than once in the CREATE TABLE
statement. 
>>
>>Original: 42Y04|Cannot create a procedure or function with EXTERNAL NAME '{0}' because
it is not a dot separated list. The expected format is <full java path>.<method name>.
>>Changed to: 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>.
>>
>>Original: 42Y13|Column name '{0}' appears more than once in the create view statement.
>>Changed to: 42Y13|Column name '{0}' appears more than once in the CREATE VIEW statement.
>>
>>Original: 42Y16|No public static method '{0}' was found in class '{1}'.  It may be
that the method exists, but it is not public, or not static.
>>Changed to: 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. 
>>
>>Original: 42Y29|The SELECT list of a non-grouped query contains at least 1 invalid
expression.  When the SELECT list contains at least 1 aggregate then all entries must be valid
aggregate expressions.   
>>Changed to: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.
>>
>>Original: 42Y30|The SELECT list of a grouped query contains at least 1 invalid expression.
 For a SELECT with a GROUP BY, the SELECT list may only contain grouping columns and valid
aggregate expressions. 
>>Changed to:  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.  
>>
>>Original: 42Y36|Column reference '{0}' is invalid.  For a SELECT with a GROUP BY,
the SELECT list may only contain grouping columns and valid aggregate expressions.
>>Changed to: 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.  
>>
>>Original: 42Y44|Invalid key, '{0}', specified in Properties list in FROM list. The
currently supported case-sensitive keys are '{1}'. 
>>Changed to: 42Y44|Invalid key '{0}' specified in the Properties list of a FROM list.
The case-sensitive
>>keys that are currently supported are '{1}'. 
>>
>>Original: 42Y56|Invalid joinStrategy, '{0}', specified in Properties list on table
'{1}'. The currently supported values for joinStrategy are 'hash', 'nestedloop'.
>>Changed to: 42Y56|Invalid join strategy '{0}' specified in Properties list on table
'{1}'. The
>>currently supported values for a join strategy are: <codeblock>hash</codeblock>
and <codeblock>nestedloop</codeblock>.
>>
>>Original: 42Y64|bulkFetch value of '{0}' is invalid: the minimum value for bulkFetch
is 1.
>>Changed to: 42Y64|bulkFetch value of '{0}' is invalid. The minimum value for bulkFetch
is 1.
>> 
>>Original: 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 ExternalVirtualTables, each of
which references the other, and so the statement cannot be evaluated.   
>>Changed to: 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.  
>>
>>Original: 42Y70|The user specified join order is not a legal join order. This may
be due to a join column from an inner table being passed as a parameter to an external virtual
table. 
>>changed to: 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.
>>
>>Original: 42Y90|FOR UPDATE is not permitted on this type of statement. 
>>Changed to: 42Y90|FOR UPDATE is not permitted in this type of statement.  
>>
>>Original: 42Y94|An AND or OR has a non-Boolean operand. The operands of AND and OR
must evaluate to TRUE, FALSE, or UNKNOWN. 
>>Changed to: 42Y94|An AND or OR has a non-boolean operand. The operands of AND and
OR must evaluate to TRUE, FALSE, or UNKNOWN.  
>>
>>Original: 42Z15|Invalid Type specified for column '{0}'. The type of a column may
not be changed. 
>>Changed to: 42Z15|Invalid type specified for column '&lt;<i>columnName</i>>'.
The type of a column may not be changed.  
>>
>>Original: 42Z17|Invalid Length specified for Column '{0}'. Length must be greater
than the current column length 
>>Changed to:42Z17|Invalid length specified for column '{0}'. Length must be greater
than the current column length.
>>
>>Original: 42Z18|Column '{0}' is part of a foreign key constraint '{1}'. To alter the
length of this column, you should drop the constraint first, perform the ALTER TABLE and then
recreate the constraint. 
>>Changed to: 42Z18| Column '{0}' is part of a foreign key constraint '{1}'. To alter
the length of this column, you should drop the constraint first, perform the ALTER TABLE,
and then recreate the constraint.
>>
>>Original: Column '{0}' is being referenced by atleast one foreign key constraint '{1}'.
To alter the length of this column, you should drop referencing constraints, perform the ALTER
TABLE and then recreate the constraints. 
>>Changed to: Column '{0}' is being referenced by at least one foreign key constraint
'{1}'. To alter the length of this column, you should drop referencing constraints, perform
the ALTER TABLE, and then recreate the constraints.
>>
>>Original: 42Z25|INTERNAL ERROR identity Counter: Update was called without arguments
with current value = NULL. 
>>Changed to: 42Z25|INTERNAL ERROR identity counter. Update was called without  arguments
with current value = NULL.
>>
>>Original: 42Z91|subquery
>>Changed to: 42Z91|Subquery. 
>>
>>Original: 42Z92|repeatable read 
>>Changed to: 42Z92|Repeatable read.
>>
>>Original: 42Z93|Constraints '{0}' and '{1}' have same set of columns, which is not
allowed.
>>Changed to:  42Z93|Constraints '{0}' and '{1}' have the same set of columns, which
is not allowed. 
>>
>>Original: 42Z9A|read uncommitted
>>Changed to: 42Z9A|Read uncommitted.
>>
>>Original: 42Z9B|The external virtual table interface does not support blob or clob
columns. '{0}' column '{1}'.
>>Changed to: 42Z9B|The external virtual table interface does not support BLOB or CLOB
columns. '{0}' column '{1}'. 
>>
>>Original: 42Z9F|Too many indexes ({0}) on the table {1}. the limit is {2}. 
>>Changed to: 42Z9F|Too many indexes ({0}) on the table {1}. The limit is {2}.  
>>
>>Original: X0X0E|Column position '{0}' listed in auto-generated column selection array
not found in the insert table.
>>Changed to: X0XOE| The column position '{0}' listed in the auto-generated column selection
array was not found in the insert table. 
>>
>>Original: X0X10|The USING clause returned more than one row, only single row ResultSets
are permissable.  
>>Changed to: X0X10|The USING clause returned more than one row; only single-row ResultSets
are permissible.
>>
>>Original: X0X11|The USING clause did not return any results, no parameters can be
set. 
>>Changed to: X0X11|The USING clause did not return any results so no parameters can
be set. 
>> 
>>Original: X0X67|Columns of type '{0}' may not be used in CREATE INDEX, ORDER BY, GROUP
BY, UNION, INTERSECT, EXCEPT or DISTINCT, because comparisons are not supported for that type.

>>Changed to: X0X67|Columns of type '{0}' may not be used in CREATE INDEX, ORDER BY,
GROUP BY,UNION, INTERSECT, EXCEPT or DISTINCT statements because comparisons are notsupported
for that type.
>>
>>Original: X0Y41|Constraint '{0}' is invalid: referenced table {1} has no primary key.
 Either add a primary key to {1} or explicity specify the columns of a unique constraint that
this foreign key references. 
>>Changed to: X0Y41|Constraint '{0}' is invalid bec the referenced table {1} has no
primary key.  Either add a primary key to {1} or explicitly specify the columns of a unique
constraint that this foreign key references. 
>>
>>Original: X0Y45|Foreign key constraint '{0}' cannot be added to or enabled on table
{1} because 1 or more foreign keys do not have matching referenced keys.  
>>Changed to: X0Y45|Foreign key constraint '{0}' cannot be added to or enabled on table
{1} because one or more foreign keys do not have matching referenced keys.  
>>
>>Original: X0Y57|A non-nullable column cannot be added to table '{0}' because the table
contains at least 1 row.  Non-nullable columns can only be added to empty tables.      
>>Changed to: X0Y57| A non-nullable column cannot be added to table '{0}' because the
table contains at least one row. Non-nullable columns can only be added to empty tables.
>>
>>Original: X0Y63|The command on table '{0}' failed. Null data found in the primary
key or unique constraint/index column(s). All columns in a primary or unique index key must
be non null.
>>Changed to: X0Y63|The command on table '{0}' failed because null data was found in
the primary key or unique constraint/index column(s). All columns in a primary or unique index
key must not be null.  
>>
>>Original: X0Y77|Cannot issue set transaction isolation statement on a global transaction
that is in progress because it would have implicitly commited the global transaciton.
>>Changed to: X0Y77| Cannot issue set transaction isolation statement on a global transaction
that is in progress because it would have implicitly committed the global transaction.
>>
>>Original: XBCA0|Cannot create new object with key {1} in {0} cache, it already exist
in the cache. 
>>Changed to: XBCA0|Cannot create new object with key {1} in {0} cache. The object already
exists in the cache. 
>>
>>Original: XBCX0|Exception from Cryptography provider, see next exception for details.
>>Changed to: XBCX0|Exception from Cryptography provider. See next exception for details.
>>
>>Original: XBCX2|Initializing cipher with a boot password that is too short, must be
at least {0} characters long
>>Changed to: XBCX2|Initializing cipher with a boot password that is too short. The
password must be at least {0} characters long.    
>>
>>Original: XBCX9|Cannot change boot password for a read only database.
>>Changed to: XBCX9|Cannot change boot password for a read-only database.  
>>Original: XBCXJ|The application is using a version of the Java Cryptography Extension
(JCE) earlier than 1.2.1.  Please upgrade to JCE 1.2.1 and re-try the operation. 
>>Changed to:
>> XBCXJ|The application is using a version of the Java Cryptography Extension (JCE)
earlier than 1.2.1.  Please upgrade to JCE 1.2.1 and try the operation again.    
>>
>>Original: XBCXK|The given encryption key does not match the encryption key used when
creating the database. Please ensure that you are using the correct encryption key and re-try.
 
>>Changed to: XBCXK|The given encryption key does not match the encryption key used
when creating the database. Please ensure that you are using the correct encryption key and
try again. 
>>
>>Original: XBCXL|The verification process for the encryption key was not successful,
see next exception for details. Possible causes can be an error when accessing the appropriate
file to do the verification process. 
>>Changed to: XBCXL|The verification process for the encryption key was not successful.
This could have been caused by an error when accessing the appropriate file to do the verification
process.  See next exception for details.  
>> 
>>Original: XBM01|Startup failed due to an exception, see next exception for details.
      
>>Changed to: XBM01|Startup failed due to an exception. See next exception for details.

>>
>>Original: XBM06|Startup failed, an encrypted database cannot be accessed without the
correct boot password.  
>>Changed to: XBM06|Startup failed. An encrypted database cannot be accessed without
the correct boot password.  
>>
>>Original: XBM07|Startup failed, boot password must be at least 8 bytes long.
>>Changed to: XBM07|Startup failed. Boot password must be at least 8 bytes long.
>>
>>Original: XBM0G|Failed to start encryption engine. Please make sure you are running
Java 2 and have downloaded an encryption provider such as jce and put it in your classpath.
 
>>Changed to: XBM0G|Failed to start encryption engine. Please make sure you are running
Java 2 and have downloaded an encryption provider such as jce and put it in your class path.

>>
>>Original: XBM0N|JDBC Driver registration with java.sql.DriverManager failed, see next
exception for details.
>>Changed to: XBM0N|JDBC Driver registration with java.sql.DriverManager failed. See
next exception for details. 
>>
>>Original: XBM0P|Service provider is read-only, operation not permitted. 
>>Changed to: XBM0P|Service provider is read-only. Operation not permitted. 
>>
>>Original: XBM0R|Unable to remove File {0}.
>>changed to: XBM0R|Unable to remove File {0}.  
>>
>>Original: XBM0T|Ambigious sub-protocol for database name {0}. 
>>Changed to: XBM0T|Ambiguous sub-protocol for database name {0}.   
>>
>>Original:XBM0U|No class was registered for identifier {0}
>>Changed to:XBM0U|No class was registered for identifier {0}.
>>
>>Original: XBM0V|An exception was thrown while loading class {1} registered for identifier
{0}
>>Changed to: XBM0V|An exception was thrown while loading class {1} registered for identifier
{0}.
>>
>>Original: XBM0W|An exception was thrown while creating an instance of class {1} registered
for identifier {0} 
>>Changed to: XBM0W|An exception was thrown while creating an instance of class {1}
registered for identifier {0}.
>>
>>Original: XCL01|Result set does not return rows; operation {0} not permitted. 
>>Changed to: XCL01|ResultSet does not return rows. Operation {0} not permitted. 
>>
>>Original: XCL09|An Activation was passed to the '{0}' method that does not match the
PreparedStatement. 
>>Changed to: XCL09|An activation was passed to the '{0}' method that does
>>not match the PreparedStatement. 
>>
>>Original: XCL10|A PreparedStatement has been recompiled, and the parameters have changed.
 If you are using JDBC, you must re-prepare the statement. 
>>Changed to: XCL10|A PreparedStatement has been recompiled and the parameters have
changed. If you are using JDBC you must prepare the statement again.  
>>
>>Original: XCL16|ResultSet not open, operation '{0}' not permitted. Verify that autocommit
is OFF. 
>>Changed to: XCL16|ResultSet not open. Operation '{0}' not permitted. Verify that autocommit
is OFF.
>>
>>Original: XCL22|Parameter {0} cannot be be registered as an OUT parameter because
it is an IN parameter.
>>Changed to: XCL22|Parameter {0} cannot be registered as an OUT parameter because it
is an IN parameter. 
>>
>>Original:XCL36|the delete rule of foreign key  must be {0}. (The referential constraint
is self-referencing and an existing self-referencing constraint has the indicated delete rule
(NO ACTION, RESTRICT or CASCADE).)  
>>Changed to: XCL36|The delete rule of foreign key  must be {0}. (The referential constraint
is self-referencing and an existing self-referencing constraint has the indicated delete rule
(NO ACTION, RESTRICT or CASCADE).)
>>
>>Original: XCL37|the delete rule of foreign key  must be {0}. (The referential constraint
is self-referencing and the table is dependent in a relationship with a delete rule of CASCADE.)
>>Changed to: XCL37|The delete rule of foreign key  must be {0}. (The referential constraint
is self-referencing and the table is dependent in a relationship with a delete rule of CASCADE.)
>> 
>>Original: XCL39|the delete rule of foreign key can not be CASCADE. (A self-referencing
constraint exists with a delete rule of SET NULL, NO ACTION or RESTRICT.)
>>Changed to: XCL39|The delete rule of foreign key cannot be CASCADE. (A self-referencing
constraint exists with a delete rule of SET NULL, NO ACTION or RESTRICT.) 
>>
>>Original: XCL40|the delete rule of foreign key can not be CASCADE. (The relationship
would form a cycle that would cause a table to be delete-connected to itself. One of the existing
delete rules in the cycle is not CASCADE, so this relationship may be definable if the delete
rule is not CASCADE.)
>>Changed to: XCL40|The delete rule of foreign key cannot be CASCADE. (The relationship
would form a cycle that would cause a table to be delete-connected to itself. One
>>of the existing delete rules in the cycle is not CASCADE, so this relationship
>>may be definable if the delete rule is not CASCADE.) 
>>Changed to: XCL40|The delete rule of foreign key cannot be CASCADE. (The relationship
would
>>form a cycle that would cause a table to be delete-connected to itself. One
>>of the existing delete rules in the cycle is not CASCADE, so this relationship
>>may be definable if the delete rule is not CASCADE.)  
>>
>>Original: XCL42|"CASCADE"
>>Changed to: XCL42|CASCADE
>>
>>Original: XCL43|"SET NULL" 
>>Changed to: XCL43|SET NULL
>>
>>Original: XCL44|"RESTRICT"
>>Changed to:  XCL44|RESTRICT
>>
>>Original: XCL45|"NO ACTION" 
>>Changed to: XCL45|NO ACTION
>>
>>Original: XCL46|"SET DEFAULT"
>>Changed to: XCL46|SET DEFAULT
>>
>>Original: XCL50|Upgrade of Database from a previous version is not suported.  Database
being accessed is at version level '{0}', this softare is at version level '{1}'.
>>Changed to: XCL50|Upgrading the database from a previous version is not supported.
 The database
>>being accessed is at version level '{0}', this software is at version level '{1}'.
   
>>
>>Original: XIE03|Data found on line {0} for column {1} after the stop delimiter. 
>>Changed to: XIE03|Data found on line {0} for column {1} after the stop delimiter.
 
>>
>>Original: XIE05|Data file can not be null.                                       
                                            
>>Changed to: XIE05|Data file cannot be null. 
>>
>>Original: XIE07|Field & record separators cant be substring of each other. 
>>Changed to: XIE07|Field and record separators cannot be substrings of each other.

>>
>>Original: XIE08|There is no column by name: {0}
>>Changed to: XIE08|There is no column named: {0}.  
>>
>>Original: XIE09|Total number of columns in the row are: {0} 
>>Changed to: The total number of columns in the row is: {0}.  
>>
>>Original: XIE0B|Column '{0}' in the table is of type {1}, it is not supported by import/export.
 
>>Changed to: XIE0B|Column '{0}' in the table is of type {1}, it is not supported by
the import/export feature.   
>>
>>Original: XIE0D|Can't find record separator on line {0} 
>>Changed to: XIEOD|Cannot find the record separator on line {0}.
>>
>>Original: XIE0E|Read endOfFile at unexpected place on line {0} 
>>changed to: XIEOE|Read endOfFile at unexpected place on line {0}.
>>
>>Original:XIE0I|Got IOException while writing data to the file 
>>Changed to: XIE0I|An IOException occurred while writing data to the file.
>>
>>Original: XIE0M|Table '{0}' does not exist. 
>>Changed to: XIE0M|Table '{0}' does not exist.  
>>
>>Original: XJ069 | No SetXXX methods allowed in case of Execute Statement Using.
>>Changed to: XJ069 | No SetXXX methods allowed in case of USING execute statement.
>>
>>Original: XJ071 | Zero or negative length argument '{0}' passed in a Blob or
>>Clob method.
>>Changed to: XJ071 | Zero or negative length argument '{0}' passed in a BLOB or
>>CLOB method.
>>
>>Original: XJ072 | Null pattern or searchStr passed in to a Blob or Clob
>>position method.
>>Changed to: XJ072 | Null pattern or searchStr passed in to a BLOB or CLOB
>>position method.
>>
>>Original: XJ073 | The data in this Blob or Clob is no longer available.
>>Possible reasons are that its transaction committed, or its connection closed.
>>Changed to: XJ073 | The data in this BLOB or CLOB is no longer available.
>>The BLOB or CLOB's transaction may be committed, or its connection is closed.
>>
>>Original: XJ076 | The position argument '{0}' exceeds the size of the Blob/Clob. 

>>Changed to:  XJ076 | The position argument '{0}' exceeds the size of the BLOB/CLOB.
>>
>>
>>Original: XJ077 | Got an exception when trying to read the first byte/character of
the
>>Blob/Clob pattern using getBytes/getSubString.  
>>Changed to: XJ077 | Got an exception when trying to read the first byte/character
of the
>>BLOB/CLOB pattern using getBytes/getSubString.
>>
>>Original: XJ080 | Execute Statement Using passed {0} parameters rather than {1}. 
 
>>Changed to: XJ080 | USING execute statement passed {0} parameters rather than {1}.

Mime
View raw message