Hi Simon,
according to [1], basex supports a maximum of 2^15 #ENames per database. Would there be any feedback (warning / error message / exit from processing) if this limit was exceed?
Yes, you'll get an error as soon as the limit is exceeded.
It could be, however, that the limit check is not yet enforced in all update operations. How do you store your XSLT data in the database? And could you check if you are close to the limit (e.g. via distinct-values(//*/name()), or by looking at the database statistics) ?
Thanks, Christian
If not: Could this be an explaination for turning the output of a xslt (xml => xml) to be not well-formed (The xslt itself is mature and has been used in exactly the same environment in several projects for > 2 years without problems.)? Now, with the latest project, an export of the database after the (seemingly issue-free) xslt-transform delivers e.g. elements at positions where they should not appear / opening elements not fitting their closing counterparts / missing content at the end? All other projects are ok with the current setup, but have significantly less data. The output dialect is somewhat "creative" and prone to resulting in a diversity of ENames, so this triggered my suspicion here...
I am using basex 8.2.3 on Java 1.8.51 / 64bit. Also tried with 8.0.2, but same issue there. The transformations are triggered by a small snippet of xquery sent from a basexclient to the server.
Thanks, Simon