Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would like to create a Java library without any dependency, but it needs to use an embedded SQL database. Is it good practice to package both the binary database file and the driver to access it inside the JAR file? What are some advantages and disadvantages?
Go on, it’s a widely adopted practice used by Hibernate for example.
For a memory constrained devices:
Then do not use embedded database at all. Try using ThoughtWorks library XStream which serializes/deserializes objects to XML/jSon which can be stored in files. Very effective solution with a small memory foot print.