Just be aware, that adding extra whitespace are not always "correct"
because it depends on the parsemode wheather white space are "eaten up".
See http://www.w3schools.com/schema/schema_facets.asp section
"Restrictions on Whitespace Characters" so if there is a length
restition together with the "preserve" flag set a (normally) correct
formated XML might fail validation or even worse if the apllication
explicitly relies on the whitespace (for example user written text) and
they are not removed/collapsed like in (X)HTML would lead to different
output and the user might be confised that its input "magically changes"
after save/reload from storage.
Am 12.12.2011 19:07, schrieb Thomas Mueller:
Hi,
For my use case, it's a feature :-) The generated XHTML looks better.
Is it really a problem for you? Specially when generating XHTML.
By the way, you should use XMLTEXT or XMLCDATA to avoid XML injection:
CALL XMLNODE('a', XMLATTR('href', 'http://h2database.com'),
XMLNODE('b', null, XMLTEXT('H' || CHR(13) || CHR(10) || '2')));
Maybe the newline should be escaped (using &#x) when using XMLCDATA,
what do you think?
Regards,
Thomas
--
You received this message because you are subscribed to the Google
Groups "H2 Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
