db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kmars...@apache.org
Subject svn commit: r629909 - /db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita
Date Thu, 21 Feb 2008 18:37:49 GMT
Author: kmarsden
Date: Thu Feb 21 10:37:49 2008
New Revision: 629909

URL: http://svn.apache.org/viewvc?rev=629909&view=rev
Log:
DERBY-2653 (doc) Expose existing auto-generated key functionality through more JDBC APIs in
Derby Client.

port revision 629580 from trunk.


Modified:
    db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita

Modified: db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita?rev=629909&r1=629908&r2=629909&view=diff
==============================================================================
--- db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita (original)
+++ db/derby/docs/branches/10.3/src/ref/crefjavstateautogen.dita Thu Feb 21 10:37:49 2008
@@ -42,13 +42,13 @@
 <li>An array of the names of the columns in the inserted row that should be
  made available.  If any column name in the array does <i>not</i> designate
 an  auto-increment column, <ph conref="../conrefs.dita#prod/productshortname"></ph>

-will throw an error. (This argument is supported only with the  <ph conref="../conrefs.dita#prod/productshortname"></ph>
embedded
-driver.) </li>
+will throw an error with the  <ph conref="../conrefs.dita#prod/productshortname"></ph>
embedded
+driver. With the client driver, the one element column name is ignored currently and the
value returned corresponds to the identity column. To ensure compatibility with future changes
an application should ensure the column described is the identity column. If the column name
corresponds to another column or a non-existent column then future changes may result in a
value for a different column being returned or an exception being thrown.  </li>
 <li>An array of the positions of the columns in the inserted row that should
 be  made available. If any column position in the array does <i>not</i> correlate
  to an auto-increment column,  <ph conref="../conrefs.dita#prod/productshortname"></ph>
will
-throw an error.  (This argument is supported only with the  <ph conref="../conrefs.dita#prod/productshortname"></ph>
embedded
-driver.) </li>
+throw an error with the  <ph conref="../conrefs.dita#prod/productshortname"></ph>
embedded
+driver. With the client driver, the one element position array is ignored currently and the
value returned corresponds to the identity column. To ensure compatibility with future changes
an application should ensure the column described is the identity column. If the position
corresponds to another column or a non-existent column then future changes may result in a
value for a different column being returned or an exception being thrown. </li>
 </ul>
 <section><title>Example</title> <p>Assume that we have a table TABLE1
defined
 as follows:</p> <codeblock>CREATE TABLE TABLE1 (C11 int, C12 int GENERATED ALWAYS
AS IDENTITY)



Mime
View raw message