You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by fu...@apache.org on 2008/05/03 02:47:13 UTC
svn commit: r652959 -
/db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita
Author: fuzzylogic
Date: Fri May 2 17:47:12 2008
New Revision: 652959
URL: http://svn.apache.org/viewvc?rev=652959&view=rev
Log:
Update SQLState documentation for 10.3.3
Modified:
db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita
Modified: db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita?rev=652959&r1=652958&r2=652959&view=diff
==============================================================================
--- db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita (original)
+++ db/derby/docs/branches/10.3/src/ref/rrefexcept71493.dita Fri May 2 17:47:12 2008
@@ -275,11 +275,39 @@
<entry colname="col2">User '<varname><authorizationID></varname>' cannot hard upgrade database '<varname><databaseName></varname>'. Only the database owner can perform this operation.</entry>
</row>
<row>
+ <entry colname="col1">08004</entry>
+ <entry colname="col2">Connection refused to database '<varname><databaseName></varname>' because it is in replication slave mode.</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
+ <entry colname="col2">A network protocol error was encountered and the connection has been terminated: <varname><error></varname></entry>
+ </row>
+ <row>
<entry colname="col1">08006</entry>
<entry colname="col2">An error occurred during connect reset and the connection has been terminated. See chained exceptions for details.</entry>
</row>
<row>
<entry colname="col1">08006</entry>
+ <entry colname="col2"> SocketException: '<varname><error></varname>'</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
+ <entry colname="col2">A communications error has been detected: <varname><error></varname>.</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
+ <entry colname="col2">An error occurred during a deferred connect reset and the connection has been terminated. See chained exceptions for details.</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
+ <entry colname="col2">Insufficient data while reading from the network - expected a minimum of <varname><number></varname> bytes and received only <varname><number></varname> bytes. The connection has been terminated.</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
+ <entry colname="col2">Attempt to fully materialize lob data that is too large for the JVM. The connection has been terminated.</entry>
+ </row>
+ <row>
+ <entry colname="col1">08006</entry>
<entry colname="col2">Database '<varname><databaseName></varname>' shutdown.</entry>
</row>
</tbody>
@@ -920,7 +948,7 @@
</row>
<row>
<entry colname="col1">42818</entry>
- <entry colname="col2">Comparisons between '<varname><type></varname>' and '<varname><type></varname>' are not supported.</entry>
+ <entry colname="col2">Comparisons between '<varname><type></varname>' and '<varname><type></varname>' are not supported. Types must be comparable. String types must also have matching collation. If collation does not match, a possible solution is to cast operands to force them to the default collation (e.g. select tablename from sys.systables where CAST(tablename as VARCHAR(128)) = 'T1')</entry>
</row>
<row>
<entry colname="col1">42820</entry>
@@ -959,6 +987,14 @@
<entry colname="col2">The ORDER BY clause of a SELECT UNION statement only supports unqualified column references and column position numbers. Other expressions are not currently supported.</entry>
</row>
<row>
+ <entry colname="col1">42879</entry>
+ <entry colname="col2">The ORDER BY clause may not contain column '<varname><columnName></varname>', since the query specifies DISTINCT and that column does not appear in the query result.</entry>
+ </row>
+ <row>
+ <entry colname="col1">4287A</entry>
+ <entry colname="col2">The ORDER BY clause may not specify an expression, since the query specifies DISTINCT.</entry>
+ </row>
+ <row>
<entry colname="col1">42884</entry>
<entry colname="col2">No authorized routine named '<varname><routineName></varname>' of type '<varname><type></varname>' having compatible arguments was found.</entry>
</row>
@@ -1890,26 +1926,6 @@
</row>
<row>
<entry colname="col1">58009</entry>
- <entry colname="col2">SocketException: '<varname><error></varname>'</entry>
- </row>
- <row>
- <entry colname="col1">58009</entry>
- <entry colname="col2">A communications error has been detected: <varname><error></varname>.</entry>
- </row>
- <row>
- <entry colname="col1">58009</entry>
- <entry colname="col2">An error occurred during a deferred connect reset and the connection has been terminated. See chained exceptions for details.</entry>
- </row>
- <row>
- <entry colname="col1">58009</entry>
- <entry colname="col2">Insufficient data while reading from the network - expected a minimum of <varname><number></varname> bytes and received only <varname><number></varname> bytes. The connection has been terminated.</entry>
- </row>
- <row>
- <entry colname="col1">58009</entry>
- <entry colname="col2">Attempt to fully materialize lob data that is too large for the JVM. The connection has been terminated.</entry>
- </row>
- <row>
- <entry colname="col1">58009</entry>
<entry colname="col2">Network protocol exception: SCLDTA length, <varname><length></varname>, is invalid for RDBCOLID. The connection has been terminated.</entry>
</row>
<row>
@@ -1921,10 +1937,6 @@
<entry colname="col2">Network protocol exception: PKGNAMCSN length, <varname><length></varname>, is invalid at SQLAM <varname><value></varname>. The connection has been terminated.</entry>
</row>
<row>
- <entry colname="col1">58009</entry>
- <entry colname="col2">A network protocol error was encountered and the connection has been terminated: <varname><error></varname></entry>
- </row>
- <row>
<entry colname="col1">58010</entry>
<entry colname="col2">A network protocol error was encountered. A connection could not be established because the manager <varname><value></varname> at level <varname><value></varname> is not supported by the server. </entry>
</row>
@@ -1980,6 +1992,10 @@
<entry colname="col2">Cannot remove jar file '<varname><fileName></varname>' because it is on your derby.database.classpath '<varname><fileName></varname>'.</entry>
</row>
<row>
+ <entry colname="col1">X0X0D</entry>
+ <entry colname="col2">Invalid column array length '<varname><columnArrayLength></varname>'. To return generated keys, column array must be of length 1 and contain only the identity column.</entry>
+ </row>
+ <row>
<entry colname="col1">X0X0E</entry>
<entry colname="col2">Table '<varname><tableName></varname>' does not have an auto-generated column at column position '<varname><columnPosition></varname>'.</entry>
</row>
@@ -2485,6 +2501,10 @@
<entry colname="col2">Supplied value '<varname><value></varname>' for collation attribute is invalid, expecting UCS_BASIC or TERRITORY_BASED.</entry>
</row>
<row>
+ <entry colname="col1">XBM04</entry>
+ <entry colname="col2">Collator support not available from the JVM for the database's locale '<varname><value></varname>'.</entry>
+ </row>
+ <row>
<entry colname="col1">XBM0Y</entry>
<entry colname="col2">Backup database directory <varname><directoryName></varname> not found. Please make sure that the specified backup path is right.</entry>
</row>
@@ -2913,6 +2933,14 @@
<entry colname="col1">XIE0R</entry>
<entry colname="col2">Import error on line <varname><lineNumber></varname> of file <varname><fileName></varname>: <varname><details></varname> </entry>
</row>
+ <row>
+ <entry colname="col1">XIE0S</entry>
+ <entry colname="col2">The export operation was not performed, because the specified output file (<varname><fileName></varname>) already exists. Export processing will not overwrite an existing file, even if the process has permissions to write to that file, due to security concerns, and to avoid accidental file damage. Please either change the output file name in the export procedure arguments to specify a file which does not exist, or delete the existing file, then retry the export operation.</entry>
+ </row>
+ <row>
+ <entry colname="col1">XIE0T</entry>
+ <entry colname="col2">The export operation was not performed, because the specified large object auxiliary file (<varname><fileName></varname>) already exists. Export processing will not overwrite an existing file, even if the process has permissions to write to that file, due to security concerns, and to avoid accidental file damage. Please either change the large object auxiliary file name in the export procedure arguments to specify a file which does not exist, or delete the existing file, then retry the export operation.</entry>
+ </row>
</tbody>
</tgroup>
</table>