Army wrote:
I made the following addition to the end of the serializeToString()
method in SqlXmlUtil.java and was able to get consistent results (i.e.
exactly the same characters) across platforms:
+String eol = PropertyUtil.getSystemProperty(line.separator);
+if (eol != null)
+
Daniel John Debrunner wrote:
I was thinking more generally in that an XML value may be generated and
thus never have been stored to disk. How it is stored on disk and how
the XML value is serialized using XMLSERIALIZE() are different
operations, it's just an implementation detail of derby that
As part of my work for DERBY-1758 I'm looking at the XML binding test
(lang/xmlBinding.java in the old harness, lang/XMLBindingTest.java in JUnit) and
I noticed that the test, which counts characters as a simple sanity check for
insertion of docs larger than 32k, returns different results on
Daniel John Debrunner wrote:
Aren't there two separate (but related) issues here?
1) What Derby stores on disk (the extra number of characters stored)
2) How Derby serialized XML values back to an application (the test
counting issue).
Serialization of XML values can be expensive, so in
this sounds like it might be the same platform-difference problem
Forrest runs into and that affects the Derby web site:
http://db.apache.org/derby/papers/derby_web.html#odd_diffs
FOR-492 references a workaround, but I haven't looked at it, don't know
if it could apply to Derby.
-jean
Army
Jean T. Anderson wrote:
this sounds like it might be the same platform-difference problem
Forrest runs into and that affects the Derby web site:
http://db.apache.org/derby/papers/derby_web.html#odd_diffs
Yep, that looks like the same problem. Thank you for the reference!
FOR-492
Army wrote:
Daniel John Debrunner wrote:
Aren't there two separate (but related) issues here?
1) What Derby stores on disk (the extra number of characters stored)
2) How Derby serialized XML values back to an application (the test
counting issue).
Serialization of XML values can be
My question, then, is this: Is it considered a bug in Derby if
insertion of the same XML value by the user can lead to different data
I'm not much of an expert in this area, but it's my understanding that, in the
XML world, when people are trying to discuss equivalency of two XML documents,
