Possible bug in GUI corrupts database
Monday, 2 May 2011 · 4 messages · last reply 8 May 2011
TK
Thomas Kaltofen2 May 2011 13:58 #
Hi,
I think I found a bug in the GUI which corrupts the database. Steps to reproduce:
- Create database 'db1'
- Add some documents to database 'db1' through server interface (not through GUI)
- Now start GUI and open 'db1'
- Add some more documents to database 'db1' through server interface (keep GUI open)
- If one re-opens 'db1' now in GUI, database gets corrupted and GUI goes crazy
Best regards,
Thomas
CG
Christian Grün2 May 2011 14:03 #
Hi Thomas,
thanks for your observation. It is important to know that the GUI cannot be concurrently used with the server interface; see e.g. here:
http://docs.basex.org/wiki/Startup#BaseX_GUI
We might split the client/server and GUI in future versions of BaseX to avoid confusion.
Hope this helps,
Christiab
Quoted text · Thomas Kaltofen · 14 lines
On Mon, May 2, 2011 at 1:58 PM, Thomas Kaltofen <Thomas.Kaltofen at risc.uni-linz.ac.at> wrote: > Hi, > > I think I found a bug in the GUI which corrupts the database. Steps to reproduce: > > - Create database 'db1' > - Add some documents to database 'db1' through server interface (not through GUI) > - Now start GUI and open 'db1' > - Add some more documents to database 'db1' through server interface (keep GUI open) > - If one re-opens 'db1' now in GUI, database gets corrupted and GUI goes crazy > > Best regards, > Thomas
___________________________
Christian Grün
Uni KN, Box 188
78457 Konstanz, Germany
http://www.inf.uni-konstanz.de/~gruen
TK
Thomas Kaltofen2 May 2011 17:40 #
Hi Christian,
thanks for the clarification, I haven't read that so far. I was just surprised that the GUI corrupts the data although I was not performing any write operations in the GUI. I will avoid using GUI and server at the same time then.
Best regards,
Thomas
Quoted text · Christian Grün · 32 lines
-----Original Message----- From: Christian Grün [mailto:christian.gruen at gmail.com] Sent: Monday, May 02, 2011 2:03 PM To: thomas at kaltofen.at; Thomas Kaltofen Cc: basex-talk at mailman.uni-konstanz.de Subject: Re: [basex-talk] Possible bug in GUI corrupts database Hi Thomas, thanks for your observation. It is important to know that the GUI cannot be concurrently used with the server interface; see e.g. here: http://docs.basex.org/wiki/Startup#BaseX_GUI We might split the client/server and GUI in future versions of BaseX to avoid confusion. Hope this helps, Christiab On Mon, May 2, 2011 at 1:58 PM, Thomas Kaltofen <Thomas.Kaltofen at risc.uni-linz.ac.at> wrote: > Hi, > > I think I found a bug in the GUI which corrupts the database. Steps to reproduce: > > - Create database 'db1' > - Add some documents to database 'db1' through server interface (not > through GUI) > - Now start GUI and open 'db1' > - Add some more documents to database 'db1' through server interface > (keep GUI open) > - If one re-opens 'db1' now in GUI, database gets corrupted and GUI > goes crazy > > Best regards, > Thomas Christian Grün Uni KN, Box 188 78457 Konstanz, Germany http://www.inf.uni-konstanz.de/~gruen
CG
Christian Grün8 May 2011 13:39 #
Dear Thomas,
I had another look on our storage patterns and noticed that, in the case you mentioned, an outdated file length was written by the GUI instance if the same files were modified by another instance. The issue should now be solved; please check out the latest snapshot (it's very close to the next official release):
http://files.basex.org/releases/latest/
As a general note, we still generally discourage using the GUI and the C/S architecture on the same DB instances, as, e.g., interactions in the GUI might lead to concurrent, unlocked read/write access on the same files. If you know exactly what you're doing, however, it shouldn't cause any problems.
Hope this helps,
Christian
___________________________
Christian Grün
Uni KN, Box 188
78457 Konstanz, Germany
http://www.inf.uni-konstanz.de/~gruen
Quoted text · Thomas Kaltofen · 52 lines
On Mon, May 2, 2011 at 5:40 PM, Thomas Kaltofen <Thomas.Kaltofen at risc.uni-linz.ac.at> wrote: > Hi Christian, > > thanks for the clarification, I haven't read that so far. I was just surprised that the GUI corrupts the data although I was not performing any write operations in the GUI. I will avoid using GUI and server at the same time then. > > Best regards, > Thomas > > -----Original Message----- > From: Christian Grün [mailto:christian.gruen at gmail.com] > Sent: Monday, May 02, 2011 2:03 PM > To: thomas at kaltofen.at; Thomas Kaltofen > Cc: basex-talk at mailman.uni-konstanz.de > Subject: Re: [basex-talk] Possible bug in GUI corrupts database > > Hi Thomas, > > thanks for your observation. It is important to know that the GUI cannot be concurrently used with the server interface; see e.g. here: > > http://docs.basex.org/wiki/Startup#BaseX_GUI > > We might split the client/server and GUI in future versions of BaseX to avoid confusion. > > Hope this helps, > Christiab > > > On Mon, May 2, 2011 at 1:58 PM, Thomas Kaltofen <Thomas.Kaltofen at risc.uni-linz.ac.at> wrote: >> Hi, >> >> I think I found a bug in the GUI which corrupts the database. Steps to reproduce: >> >> - Create database 'db1' >> - Add some documents to database 'db1' through server interface (not >> through GUI) >> - Now start GUI and open 'db1' >> - Add some more documents to database 'db1' through server interface >> (keep GUI open) >> - If one re-opens 'db1' now in GUI, database gets corrupted and GUI >> goes crazy >> >> Best regards, >> Thomas > > ___________________________ > > Christian Grün > Uni KN, Box 188 > 78457 Konstanz, Germany > http://www.inf.uni-konstanz.de/~gruen >
Written for BaseX 6.6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery