Moving from DBM to Derby

I have been using DBM (see dbm(3UCB)) databases for all my database needs. Operating on DBM databases in perl is extremely easy. They are quite fast when you do not really need a full fledged relational database. Being a bit allergic to database classes in school, I had avoided using big relational databases like Oracle or MySQL.

When I started writing a tool which gathered huge amounts of data from various sources and then cross-checked and audited them, DBM files turned out to be quite inadequate. I desperately needed a relational database.

I tried Apache Derby, a pure java implementation of a relational database. Wow! it just worked out of the box on Solaris. To start the server just run the startNetworkServer.ksh after setting the $DERBY_INSTALL path in that script. Derby can be used either in server mode or embedded in the application just like DBM databases. Derby site also has a handy and excellent SQL reference guide.

What more, netbeans has a really neat GUI way to get into the database. You could also point OpenOffice to the derby jar file, and can connect to Derby database with URL like jdbc:derby://localhost:1527/mydb1. There is also a CLI tool org.apache.derby.tools.ij.

Comments:

Why not sqlite? It is a small step up from dbm.

Posted by guest on February 27, 2006 at 09:34 AM PST #

Cool!

Also, check out Francois Orsini's description of his Derby demo for Apache Con 2005. The demo embeds Derby in a browser. I've also written about it here.

Posted by M. Mortazavi on February 27, 2006 at 01:32 PM PST #

Post a Comment:
Comments are closed for this entry.
About


sayings of an hearer

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today