Hi, Using 9.7.1 (: test transform :) let $xslt:=<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"> <xsl:template match="/"> xsl:messageI want to see all of the very long message aaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbb cccccccccccc hhhhhhhhhhhhhhhhhhhhhhhhhhhh gggggg gggggggggggggggggg aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa important bit</xsl:message> </xsl:template> </xsl:stylesheet> return xslt:transform-report(<xml/>,$xslt)?messages
Returns ["I want to see all of the very long message aaaaaaaaaaaaaaaaa
 aaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbb cccccccccccc hhhhhhhhhhhhhhhhhhhhhhhhhhhh
 gggggg gggggggggggggggggg aaaaaaaaaaaaaaaaaaa..."]
Is it BaseX truncating this? Can it be turned off for this case?
/Andy
Hi Andy,
It’s the BaseX standard serializer that truncates maps and arrays. Some more examples:
[ string-join(1 to 1000) ], map { 1: string-join(1 to 1000) }
You can get the full string by attaching a ?* lookup step to your query.
Maybe we can remove the truncation of values in function items; I’ll have some more thoughts on that.
Thanks, Christian
Ah, yes I see now. I never noticed this before. Looks good now I realise what is happening. /Andy
On Fri, 29 Apr 2022 at 19:11, Christian Grün christian.gruen@gmail.com wrote:
Hi Andy,
It’s the BaseX standard serializer that truncates maps and arrays. Some more examples:
[ string-join(1 to 1000) ], map { 1: string-join(1 to 1000) }
You can get the full string by attaching a ?* lookup step to your query.
Maybe we can remove the truncation of values in function items; I’ll have some more thoughts on that.
Thanks, Christian
basex-talk@mailman.uni-konstanz.de
-
Andy Bunce -
Christian Grün