db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Trivial Update of "ReferenceManualTenTwo" by LauraStewart
Date Mon, 02 Oct 2006 20:32:12 GMT
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 LauraStewart:
http://wiki.apache.org/db-derby/ReferenceManualTenTwo

------------------------------------------------------------------------------
  ||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 changes (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'. || Patch submitted (Laura) ||
  || 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])
|| Fixed (Laura)||
- || 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.|| Patch submitted (Laura) ||
+ || 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.|| Fixed (Laura) ||
  || 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] || Fixed (Laura) ||
  || 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. || Patch submitted (Laura) ||
+ || 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. || Fixed (Laura) ||
  || CAST function || [http://db.apache.org/derby/docs/10.2/ref/rrefsqlj33562.html rrefsqlj33562.html]
|| Susan ||  Several of the values listed in the supported CAST conversion table are incorrect
when casting to VARCHAR and TIMESTAMP.  See [http://issues.apache.org/jira/browse/DERBY-1804
DERBY-1804] || Fixed (Laura) ||
  || SECOND, SMALLINT, SUBSTR, TIMESTAMP, UCASE functions || See the following thread on [http://mail-archives.apache.org/mod_mbox/db-derby-dev/200609.mbox/%3c20060901224247.49614.qmail@web81305.mail.mud.yahoo.com%3e
derby-dev] || Susan || There are some incorrect statements or errors for all of these functions.
|| ||
  || DECLARE GLOBAL TEMPORARY TABLE || [http://db.apache.org/derby/docs/10.2/ref/rrefdeclaretemptable.html
rrefdeclaretemptable.html] || Myrna ||  1. DOUBLE is missing from list of supported Data-types
(although it's a synonym of DOUBLE PRECISION which is there, so minor, minor).  2. Following
are missing from 'the following data types cannot be used with Declared...': CHAR FOR BIT
DATA, VARCHAR FOR BIT DATA, LONG VARCHAR FOR BIT DATA.  3. The section 'Restrictions specific
to Derby' needs to be integrated into the section 'Restrictions on Declared Global Temporary
Tables'. Some items are in both places, for instance, 'Temporary tables cannot be specified
in the following statements' lists 'LOCK' and  the other section 'LOCK TABLE'. On the other
hand, CREATE INDEX is not in the list of unsupported statements, but the 'Restrictions specific
to Derby' shows that 'Indexes' are not supported. || Fixed (Laura) ||

Mime
View raw message