For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 2 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
I’m a student rather new to the whole Java DB stuff and I was wondering how you would go about creating a databse that could reside on a users machine locally but the user not need anything installed but the program that’s going to use it. Basically, I’m creating a program that needs to store user info in a DB and I want it to not have to rely on the user having to have mySQL installed on their machine in order for the program to be able to fetch from the DB. I’ve done connectivity through mySQL where it’s installed locally on my machine but never creating a DB that doesn’t need it installed. Hope I’m not rambling. If you need any more info abot it just let me know and I’ll give you as much as I can.
Moving to OT > Soft Dev
What you want is an embedded DB. These are getting quite popular in Java and you have two very robust/fast choices. One is HSQLDB: http://www.hsqldb.org/ and the other is Derby: http://db.apache.org/derby/
Thanks for the reply so fast! Actually I found Derby a little bit ago but I’ll definitely check out the other one as well. Which would you suggest has more versatility and which has more ease of use/implementation. Also, I wanna make sure, even though the DB isn’t huge, that speed isn’t sacrificed. I understand that the DB speed will be reduced due to it needing to run through the interpreter. Is this a noticable difference?
Personally I’d use HSQLDB right now. Derby was donated to Apache from IBM about 6 months ago and it’s being banged on all the time which is great, but I see more people deploying HSQLDB as an embedded db in their apps right now. Also the foot print and performance of both is really excellent. Assuming you are doing normal stuff with the DBs (sales records, employment records, etc.) Stuff like that and not millions upon millions of records, you should get some really good performance out of these things. Also I believe both provide hard-drive fall over incase the DB grows too large for memory or you want to persist it.
Google for a Derby/HSQL comparison, I have only dabbled so I’m not really qualified to suggest one or the other to you right now.
Thanks alot for your help. I’ll be sure to let you know how things turn out with it. And I’m sure I’ll be on here asking more questions since today after work I’ll be installing myEclipse to check it out. Lots o stuff I don’t know but really would like to familiarize myself with. Thanks again!
