exist
                                
                                 exist copied to clipboard
                                
                                    exist copied to clipboard
                            
                            
                            
                        eXist Native XML Database and Application Platform
Even after all the recent work. It is still possible for corruptions to occur in the Journal from concurrent transactions. This currently affects all versions of eXist-db and the same...
The Symbols Table (`symbols.dbx`) does not use the WAL (Write Ahead Journal), because each entry added to it is immediately written to its `FileOutputStream`. I imagine that the thinking was:...
### What is the problem In eXist-4.4.0 and eXist-5.0.0-RC4, when elements containing descendants that match a Lucene full-text search with `ft:query()` are expanded with `util:expand()`, this creates duplications of parts...
### What is the problem` The following XQuery gives an error message that as far as I understand things doesn't make sense: ```xquery let $col as document-node()* := collection('/db/apps/dashboard') let...
### What is the problem Saving HTML files to the database (tested with webdav, eXide and notices on deploying a .xar) eXist serializes brackets, even those inside CDATA sections. So...
Hi there, I am planning on using exist-db for my PhD Project (An Edition of early modern sources), so I decided to dive right into it. I am running Windows...
```xquery module namespace count="http://exist-db.org/xquery/test/count"; declare variable $count:TEST_COLLECTION := "/db/" || $count:TEST_COLLECTION; ```
The following very simple query from the XQTS 3.1 will result in a `java.lang.StackOverflowError`. ```xquery 3 treat as item()+ + +1 ``` It should also be considered as a security...
### What is the problem An error `java:java.lang.NullPointerException` is reported in the XQSuite output when the function tested makes a dynamic call to a function in a variable. There is...
There are several places in the eXist-db code base where we likely do not correctly handle `InterruptedException`s. For advice on handling see: https://www.ibm.com/developerworks/library/j-jtp05236/