BaseX-Talk Digest, Vol 7, Issue 6
Hi Christian,
thank you for the response.
The error occurs every time I try to import the folder when using version 6.1.
Using version 6.1.9 it doesn't throw an error but it just quits.
INFO DB gives me: Database Properties Name: tu Size: 4546 Bytes Nodes: 1 Height: 0
Database Creation Source Path: /home/tuscreen/cml Time Stamp: 29.05.2010 08:02:54 Input Size: 0 Bytes Encoding: UTF-8 Documents: 1 Whitespace Chopping: ON Entity Parsing: OFF
Indexes Path Summary: ON Text Index: ON Attribute Index: ON Full-Text Index: OFF
Patrick
Quoted text · 10 lines
> Patrick, > > thanks for your report. Have you managed to reproduce the bug (i.e., > has it occurred a second time?) As a shorthand, I'd suggest to try the > latest, stable version of BaseX, which you find at: > > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.1.9/ > > Looking forward to your feedback, > Christian
Hm, this is a really unusual behavior, as all errors are normally covered by corresponding messages – and interrupted database are usually deleted after the process has been interrupted, so that they cannot be opened afterwards. If there is any chance to make the data available for us for testing, or if you manage to trace the single documents that cause the troubles, that would be great.
Christian
Quoted text · Patrick Schäfer · 53 lines
On Thu, Jul 8, 2010 at 2:56 PM, Patrick Schäfer <patrick.schaefer at zib.de> wrote: > Hi Christian, > > thank you for the response. > > The error occurs every time I try to import the folder when using version > 6.1. > > Using version 6.1.9 it doesn't throw an error but it just quits. > > INFO DB gives me: > Database Properties > Name: tu > Size: 4546 Bytes > Nodes: 1 > Height: 0 > > Database Creation > Source Path: /home/tuscreen/cml > Time Stamp: 29.05.2010 08:02:54 > Input Size: 0 Bytes > Encoding: UTF-8 > Documents: 1 > Whitespace Chopping: ON > Entity Parsing: OFF > > Indexes > Path Summary: ON > Text Index: ON > Attribute Index: ON > Full-Text Index: OFF > > > > > Patrick > >> Patrick, >> >> thanks for your report. Have you managed to reproduce the bug (i.e., >> has it occurred a second time?) As a shorthand, I'd suggest to try the >> latest, stable version of BaseX, which you find at: >> >> http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.1.9/ >> >> Looking forward to your feedback, >> Christian > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 6. BaseX may have changed since: please check the current documentation.