[Db-derby Wiki] Update of "ReferenceManualTenTwo" by KristianWaagan

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/ReferenceManualTenTwo

------------------------------------------------------------------------------
  ||[#sql92support Derby support for SQL-92 features] ||Yip || ||
  ||[#systemtables Derby System Tables] ||Yip || ||
  ||[#exceptionmessages Derby exception messages and SQL States] || jta, Yip || ||
- ||[#jdbcref JDBC Reference] || Mamta || ||
+ ||[#jdbcref JDBC Reference] || Mamta, Kristian || ||
  ||[#settingattr Setting attributes for the database connection URL] || Mamta || ||
  ||[#j2eecompliance J2EE Compliance: Java Transaction API and javax.sql Extensions] || Susan || ||
  ||[#derbyapi Derby API] || Mamta || ||
@@ -37, +37 @@

  ||List of datatypes || [http://db.apache.org/derby/docs/dev/ref/ derv/ref]|| Dan D || In the list of data types the XML type is listed as 'XML data type', remove the words 'data type', all of the other types are listed just as the type name. Same is true of the page that describes the XML type, it says 'XML data type', other types just have the name of the type, e.g. BLOB || ||
  || XQUERY operator || [http://db.apache.org/derby/docs/dev/ref/rreffuncxmlquery.html rreffuncxmlquery.html] || Dan D || This description: ''The result of the XMLQUERY operator is another Derby XML value. Unlike other XML values, the result might represent an empty sequence of XML nodes or values. Atomic values, such as strings, can be part of the result sequence. The result of an XMLQUERY operator is not guaranteed to represent a valid XML document and it might not be possible to insert the result of an XMLQUERY operator into a Derby XML column'' should be replaced with: The result of the XMLQUERY operator is '''a value of type XML'''. '''The result represents a''' sequence of XML nodes or values. Atomic values, such as strings, can be part of the result sequence. The result of an XMLQUERY operator is not guaranteed to represent a '''well formed''' XML document and it might not be possible to insert the result of an XMLQUERY operator into an XML column  - Notes on the chang
 es (bold), a) no need to use Derby b) The old wording had the use of 'might' and 'empty sequence', I think it wanted to describe a sequence and the result is always a sequence, not that it might be. c) Use of 'well-formed' is better than 'valid'. || ||
  || Date function || [http://db.apache.org/derby/docs/dev/ref/rrefdatefunc.html ref/rrefdatefunc.html] || jta || The number listed in the description "a positive number less than or equal to 3,652,059" gets an error, the max number that works is 2,932,897 ([http://mail-archives.apache.org/mod_mbox/db-derby-dev/200608.mbox/%3c44F722C0.2060203@bristowhill.com%3e posted to derby-dev], added to [https://issues.apache.org/jira/browse/DERBY-1803 DERBY-1803]) || ||
- || XML data type || [http://db.apache.org/derby/docs/dev/ref/rrefsqljtypexml.html rrefsqljtypexml.html] || Army ||  See following thread: [http://thread.gmane.org/gmane.comp.apache.db.derby.devel/28136/focus=28136  xmlTypeThread] || ||
+ || XML data type || [http://db.apache.org/derby/docs/dev/ref/rrefsqljtypexml.html rrefsqljtypexml.html] [[BR]] || Army ||  See following thread: [http://thread.gmane.org/gmane.comp.apache.db.derby.devel/28136/focus=28136  xmlTypeThread] [[BR]] ^(KW)^Missing dot between class and methodname. Change !PreparedStatementsetCharacterStream to !PreparedStatement.setCharacterStream.|| ||
  || XML operators || [http://db.apache.org/derby/docs/dev/ref/rrefsqlj29026.html rrefsqlj29026.html] || Army ||  See following thread: [http://thread.gmane.org/gmane.comp.apache.db.derby.devel/28570/focus=28570  xmlOpsThread] || ||
  || XML Operators || various || Dan D || The XML operators and data type include text about requiring Xalan etc. When trying out XML I felt lost at this point because there was no information on what I was meant to do. It was the feeling I was being told "You need to do something with Xalan to get this to work, but you are going to have to figure that out yourself". It stopped me from evaluating Mustang with XML. Can there be information in the developers' guide about this, and a link to that information from these Usage notes? || ||
  || XMLSERIAIZE operator || [http://db.apache.org/derby/docs/dev/ref/rreffuncxmlserialize.html rreffuncxmlserialize.html ] || Susan ||  To retain consistencey in all of the XML examples the example table name should remain x_table.  When used in the XMLSERIALIZE example it was changed to xtable. || ||
@@ -74, +74 @@

  || ||  || || || ||
  ||java.sql.Blob and java.sql.Clob || [http://db.apache.org/derby/docs/10.2/ref/rrefjdbc96386.html] || Mamta || This section has a table titled Table 1. JDBC 2.0 java.sql.Blob Methods Supported. The first row, 3rd column of this table shows up empty in the html page but has an ' in the pdf format. The pdf format should also show the column empty. I think this happens for all the tables with no data in the pdf format || ||
  ||DatabaseMetaData functionality not supported || [http://db.apache.org/derby/docs/10.2/ref/ref-single.html#N2E3A9] || Mamta || This section says that getColumnPrivileges and getTablePrivileges are not supported. But checkin r381109 has changes to metadata.properties for these 2 functions. So, looks like these methods are probably now supported with grant revoke functionality. || ||
+ || Data streaming || ^(1)^[http://db.apache.org/derby/docs/dev/ref/rrefjavsqlprst.html][[BR]] ^(2)^[http://db.apache.org/derby/docs/dev/ref/rrefjavsqlrssc.html][[BR]] ^(3)^[http://db.apache.org/derby/docs/dev/ref/crefjavbclobnot.html] [[BR]] ^(4)^[http://db.apache.org/derby/docs/dev/ref/rrefjdbc4_0summary.html]|| Kristian ||(1): Rewrite section to reflect a newer JDBC version than 1.2? Comment that getUnicodeStream is deprecated and no longer implemented in Derby. Add description of getCharacterStream. Could also add info about setNCharacterStream, which is JDBC 4 only and not supported. The note under the table is no longer accurate; it only applies when using the client driver (and also only for the client?).[[BR]](2): OK [[BR]] (3): Update list of methods (mark as deprecated, add getCharacterStream). [[BR]](4): OK.|| ||
  
  
  [[Anchor(settingattr)]]'''Setting attributes for the database connection URL: '''
@@ -82, +83 @@

  || ||  || || || ||
  ||Derby database connection URL syntax || [http://db.apache.org/derby/docs/10.2/ref/ref-single.html#N2D4F2] || Mamta || The syntax of the database connection URL shows databasename as optional. Is that correct? I tried following in ij connect 'jdbc:derby:'; and got exception ERROR XJ004: Database '' not found. Actually, further reading of the reference manual shows this is not an issue. It is possible to not specify the databasename in the url and specify the database name information through a Properties object. This is covered in [http://db.apache.org/derby/docs/10.2/ref/rrefattrib17246.html]. Also, when user wants to shutdown the entire Derby system, no databasename will be specified. || ||
  ||Attributes of the Derby database connection URL || [http://db.apache.org/derby/docs/10.2/ref/ref-single.html#N2D6D9] || Mamta || This section has 3 examples of setting attributes on database connection URL using Java. One minor suggestion is we should use Java commenting scheme ie /*..*/ instead of -- in this sample code. || ||
- || encryptionKey section under Setting attributes for the database connection URL || [http://db.apache.org/derby/docs/10.2/ref/rrefattribencryptkey.html] || Mamta || The pdf page for encryptionKey has incomplete example. The pdf page only shows jdbc:derby:newDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding; The corresponding html page shows the correct example which looks as follows jdbc:derby:newDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768
+ || encryptionKey section under Setting attributes for the database connection URL || [http://db.apache.org/derby/docs/10.2/ref/rrefattribencryptkey.html] || Mamta || The pdf page for encryptionKey has incomplete example. The pdf page only shows jdbc:derby:newDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding; The corresponding html page shows the correct example which looks as follows jdbc:derby:newDB;create=true;dataEncryption=true;encryptionAlgorithm=DES/CBC/NoPadding;encryptionKey=6162636465666768 || ||
-  || ||
  
  
  [[Anchor(j2eecompliance)]]'''J2EE Compliance: Java Transaction API and javax.sql Extensions: '''