Re: Future of McKoi?
"Bayless Kirtley" <[email protected]> Mon, 28 Jan 2008 17:08:24 -0600
| Newsgroups | gmane.comp.db.mckoi |
|---|---|
| Message-ID | <006901c86203$8bdeaf70$6401a8c0@Desktop> |
------=_NextPart_000_004B_01C861D0.6445D890 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The current version of Hsqldb supports transactions only in isolation = mode READ_UNCOMMITTED. I discovered this when trying to correct the = problems brought on by updating to Java 1.6. I was trying to eliminate = any other problems that might be caused by poor application programming. = When queried, JDBC reported READ_COMMITTED mode as I had set it when = that was not actually true. As a result, I changed a lot of the = application to AUTO-COMMIT wherever it was practical. According to the = developers, the next revision will handle all transaction isolation = properly although it sounds like with some additional overhead. BTW, = Hsqldb is now handled by Sourceforge. That should be a good thing. Bayless ----- Original Message -----=20 From: M. A. Sridhar=20 To: [email protected]=20 Sent: Monday, January 28, 2008 2:57 PM Subject: Re: Future of McKoi? 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=20 m_a_sridhar at yahoo dot com ----- Original Message ---- From: Alexander Finger <[email protected]> To: [email protected] Sent: Saturday, January 26, 2008 7:29:53 PM Subject: Re: Future of McKoi? do not bother with mckoi. Check out Derby instead. On 1/26/08, Alex Molochnikov <[email protected]> wrote: > Is 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 [email protected] -------------------------------------------------------------------------= ----- No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.516 / Virus Database: 269.19.14/1247 - Release Date: = 1/28/2008 10:59 AM ------=_NextPart_000_004B_01C861D0.6445D890 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <STYLE type=3Dtext/css>DIV { MARGIN: 0px } </STYLE> <META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>The current version of Hsqldb supports = transactions=20 only in isolation mode READ_UNCOMMITTED. I discovered this when trying = to=20 correct the problems brought on by updating to Java 1.6. I was trying to = eliminate any other problems that might be caused by poor application=20 programming. When queried, JDBC reported READ_COMMITTED mode = as I had=20 set it when that was not actually true. As a result, I changed a = lot of the=20 application to AUTO-COMMIT wherever it was practical. According to the=20 developers, the next revision will handle all transaction isolation = properly=20 although it sounds like with some additional overhead. BTW, Hsqldb is = now=20 handled by Sourceforge. That should be a good thing.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Bayless</FONT></DIV> <DIV> </DIV> <BLOCKQUOTE=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A [email protected] = href=3D"mailto:[email protected]">M. A.=20 Sridhar</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A = [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, January 28, 2008 = 2:57=20 PM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Future of = McKoi?</DIV> <DIV><BR></DIV> <DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: tahoma,new = york,times,serif">I am=20 interested in the Mckoi database because I think it has been the best = one I've=20 seen among all the pure Java databases I've evaluated. I have tried = pointbase,=20 h2, hsqldb and cloudscape/derby, in the context of a fairly large CRM = app I=20 have been involved with. Each had its own set of issues. Pointbase = wasn't as=20 fast, nor was cloudscape or h2 (at the time I tested them -- a few = years ago).=20 hsqldb was actually quite a bit faster, but I seem to recall that it = wasn't=20 supporting transactions properly. I even tried sqlite, but there were = some=20 issues with blob support in its JDBC driver.<BR><BR>By contrast, I've = had=20 Mckoi deployed in production for quite a while now, and never had a = hiccup --=20 no data corruptions, no management headaches, nothing. It just works. = So it be=20 a real pity to see this project die.<BR><BR>Regards.<BR> <DIV> </DIV> <DIV=20 style=3D"BORDER-TOP: rgb(200,200,200) 1px solid; FONT-SIZE: 92%; = PADDING-BOTTOM: 4px; WIDTH: 400px; PADDING-TOP: 4px">M.=20 A. Sridhar <BR><CODE style=3D"FONT-SIZE: 92%">m_a_sridhar at yahoo dot = com</CODE></DIV> <DIV=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: tahoma,new = york,times,serif"><BR><BR> <DIV=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new = york,times,serif">-----=20 Original Message ----<BR>From: Alexander Finger=20 <[email protected]><BR>To: [email protected]<BR>Sent: = Saturday,=20 January 26, 2008 7:29:53 PM<BR>Subject: Re: Future of McKoi?<BR><BR>do = not=20 bother with mckoi. Check out Derby instead.<BR><BR>On 1/26/08, Alex=20 Molochnikov <<A href=3D"mailto:[email protected]"=20 ymailto=3D"mailto:[email protected]">[email protected]</A>>=20 wrote:<BR>> Is McKoi database still actively developed and = supported? The=20 last release<BR>> was made 3.5 years=20 = ago...<BR>><BR><BR><BR>-----------------------------------------------= ----------------<BR>Mckoi=20 SQL Database mailing list <A = href=3D"http://www.mckoi.com/database/"=20 target=3D_blank>http://www.mckoi.com/database/</A><BR>To unsubscribe, = send a=20 message to <A href=3D"mailto:[email protected]"=20 = ymailto=3D"mailto:[email protected]">mckoidb-unsubscribe@mcko= i.com</A><BR><BR></DIV><BR></DIV></DIV> <P> <HR> <P></P>No virus found in this incoming message.<BR>Checked by AVG Free = Edition. <BR>Version: 7.5.516 / Virus Database: 269.19.14/1247 - = Release Date:=20 1/28/2008 10:59 AM<BR></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_004B_01C861D0.6445D890--