These are the reasons why I am choosing JavaDB-Derby database:
- Multiplatform and free.
- Without database installation.
- It can be an embedded database, like as Ms. Access. Just copy-paste a database folder for backup.
- Support relationship.
- It has view and sequence.
- It has function, procedure, and trigger. Trust me, they 're hard.
- It can be attached a custom function from .jar. So, it can show a form/frame from .jar with SQL sintax.
- Autonumber datatype can be restart to number 1.
- It has BOOLEAN datatype.
- It has database security.
- Easily upsize to be a server database. Just moving that database folder to derbyhome/bin folder. Then run StartNetworkServer.bat or StartNetworkServer.sh. And easily downsize to be an embedded database.
- It can be stored in .jar file. Though there are a few limitation, like as: data can't be added, editted, or deleted; No database security; Using APP schema only.
This GUI using derby.jar version 10.8.1.2. If it is different from your version, replace it with your derby.jar and your derbyclient.jar.
Thanks a lot, to Apache Derby (Apache Software Foundation), and to all.