>> We are using eXist-db 1.2.0-rev:7236-20080115. Do you recommend updating
>> to a newer version, and if yes, which one?
> I'm not aware of any bugs affecting document order in 1.2 or earlier
> releases. However, 1.2.4 does contain some important bug fixes. Within the
> 1.2 series, updates should be without risk.
Finally, we managed to reproduce & track down the odd & severe
behaviour/bug of eXist-db, which changes the order of elements in XML
documents and breaks the document in other ways, too.
Bad news: The problem exists (at least) in eXist-db 1.2.0
Good news: The problem does not exists anymore in eXist-db 1.2.4
rev8072-20080802 or at least I am not able to reproduce it with my
example code. Maybe it has been fixed on purpose?!?
Anyway, I have enclosed a test database (XML document) and a test XQuery.
Put the XML document to the database (/db/testdb.xml) and change the
owger&group access rights of the document to "guest" & "guest". Finally,
execute the XQuery in XQuery Sandbox and see what happens to the "id"
attribute of the <researchareas> element. Yes, it's has disappeared and
the value of that "id" attribute has shifted between the first and second
If I will move the <researchareas> element before the <projects> element
and do the update, then everything works fine.
I was not able to figure out what is the reason for this odd behaviour,
but I would sure like to know. Like I said, eXist-db 1.2.4 works fine with
my test case.