That is interesting. I originally chose McKoi for my project and used it for the first few months of development. It started getting corrupted very early in the testing phase and did this several times. I couldn't get much help and no recovery schemes seemed to work. I switched to Hsqldb over a year ago as it had all the features of McKoi except for the Java Object data type. Actually, it turned out to be considerably faster too.
The database has been in production for almost 6 months now. A few weeks ago, I updated to Java 1.6 and started getting corrupted index or internal pointers or something. Fortunately, Hsqldb does have pretty good recovery tools so I lost almost no data. I looked at Derby, especially since Sun has adopted it as JavaDB. It is reported to be considerably slower then Hsqldb and it does not support the Boolean data type which is scattered throughout my application. The conversion would be too much.
Bayless
----- Original Message -----
From: Alexander Finger
To: ***@mckoi.com
Sent: Monday, January 28, 2008 3:01 PM
Subject: Re: Future of McKoi?
The software I worked on that had a McKoi database (implemented prior to my arrival) had many problems. Its data got corrupted often; I am surprised to hear you say you've never even had a hiccup.
Alex
On Jan 28, 2008 3:57 PM, M. A. Sridhar <***@yahoo.com> wrote:
I am interested in the Mckoi database because I think it has been the best one I've seen among all the pure Java databases I've evaluated. I have tried pointbase, h2, hsqldb and cloudscape/derby, in the context of a fairly large CRM app I have been involved with. Each had its own set of issues. Pointbase wasn't as fast, nor was cloudscape or h2 (at the time I tested them -- a few years ago). hsqldb was actually quite a bit faster, but I seem to recall that it wasn't supporting transactions properly. I even tried sqlite, but there were some issues with blob support in its JDBC driver.
By contrast, I've had Mckoi deployed in production for quite a while now, and never had a hiccup -- no data corruptions, no management headaches, nothing. It just works. So it be a real pity to see this project die.
Regards.
M. A. Sridhar
m_a_sridhar at yahoo dot com
----- Original Message ----
From: Alexander Finger <***@gmail.com>
To: ***@mckoi.com
Sent: Saturday, January 26, 2008 7:29:53 PM
Subject: Re: Future of McKoi?
do not bother with mckoi. Check out Derby instead.
Post by Alex MolochnikovIs McKoi database still actively developed and supported? The last release
was made 3.5 years ago...
---------------------------------------------------------------
Mckoi SQL Database mailing list http://www.mckoi.com/database/
To unsubscribe, send a message to mckoidb-***@mckoi.com