Using a database as backend

In the next steps of development I try to evaluate the use of a database as a backend. Storing article and group data is a serious issue for my newsreader, because there are a lot of actions you can start on your data.

First, you want to search all article for some text. Second, you want to get all article of a specific author. Third, you want to know how many article are unread.

All this requirements are best met with a database, but unfortunatly a database backend is complicated - for the user and the developer. I try to use something like HSQLDB or SQLite because I want to safe the user work. The user don't want to create a database, don't want to fiddle around with permissions and stuff. He just want to get that application started...

And that's what I want, too. So I'll evaluate SQLite and HSQLDB and try to include them into JUsenet. Be patient until my next CVS release. :)