Daobab closely integrates SQL with Java.
That's the main reason, why the DataBase usage becomes so native and quick.
Idea 'code completion' guides you safely even throughout the most sophisticated queries, and checks your query into real time.
Your work is correct, you are always certain of it.
Second great benefit is a real and complete Object Relational Mapping.
To reach that, Daobab introduced a completely new approach to the Entities DTO.
Tables, Columns... literally everything is a true object.
Literally everything, even your query, may be an abstract Java object as well.
Another thing is complexity. Daobab is almost fully compatible with SQL standard. That's extraordinary. Even some unpopular SQL Functions, are available. Even very rare SQL constructions, are possible. That brings the full scope of possibilities.
Fully Object Oriented
Entities have relations copied from the database to Java.
Abstracts and interfaces are fully in use.
Do you like to create abstract methods? You should like to create abstract SQL queries as well.
Entity as Map with column interfaces
Each unique column has its own interface. Entity has no fields, but interfaces. Each column interface reads and writes from a map.
Relations between entities (tables) are built by implementing the same column interfaces.
This unique approach brings a lot of opportunities and recreates the database relations into a Java.
With Daobab, query mostly ends in a single line.
SQL within Java code
You don't need to create a separate method for each specific query.
You may use SQL in your for loops, if conditions or generally inside of any Java method body.
SQL with values
You may log your query completely, with values.
Also you can copy and paste SQL from your log to debug it into your DB tool.
And it's safe.
There is totally no casting. All types are being handled automatically.
Easy to use
Basically, after reverse engineering, you are ready to work with the database.
Just work with queries. Don't worry about SQL assignments.
Daobab and Unit Tests? This is a perfect marriage. Just play with the queries.
Technically, you may call an unlimited amount of databases/schemas within your own microservice without any problems.
Migration? Not a big deal anymore.
Create buffers with part of the database copied into memory.
Execution of the SQL query on such a target, is very quick.
No need to have a direct database access. No need to expose a number of endpoinds.
Just execute the query remotely and safely.
No matter what kind of database you have. Daobab is able to correct your SQL and use the native database dialog.
Works fine with Spring, Spring Boot, JavaEE, standalone.... and others.