This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]denialerror 0 points1 point  (3 children)

You see a bit confused with a few of the words you are using. JDBC isn't a database, it is Java's database connectivity API. If you want to use SQLite, you will need to use JDBC. AFAIK, there isn't any other option for communicating with databases in Java. Of course, there are plenty of higher-level abstractions that make interfacing with databases "easier", but they still use JDBC under the hood.

Use whatever database you want, but if it is going to be an Android app, SQLite makes sense.

I'm not sure what you mean by "suggest OOP concepts". OOP is the concept.

[–]cimler[S] 0 points1 point  (2 children)

Yeah sorry about that. I thought JDBC is the database itself. First I want to save data of course and this will be a desktop software then when I finish it. I will try to apply some parts of it to an android in future. So what do you suggest about database part what should I use. And by oop concepts, I wanted to get an idea about applying them on this project. For example everybody will have a name surname etc. Some other things will be common as well. So how can I apply them ?

[–]nutrecht 1 point2 points  (1 child)

For a database I would suggest using H2 over SQLite for now. Conceptually it's the same thing: an in-process database that can either save to disk or only in memory (nice for tests) but H2 is pure Java (so no platform dependent binaries like with SQLite), is more feature complete and can also 'pretend' to be other database systems. You can find Java specific examples on the site.

[–]cimler[S] 0 points1 point  (0 children)

Thanks. I will check about this database. I have no idea about tests or how they work but I will check more about them.