What is the difference between jdbc and orm

But they contain the JDBC under the hood. Initially, we need to open a database connection with the help of a JDBC driver. We are executing the queries and getting the result set. In JDBC workflow the data are sent to the application via the driver manager.

When the application gets the results, it works on the processing of the data. Finally, we need to close the connection to the database. Also, every programming language requires its own specific JDBC driver. There are of cause more but the listened are the most commonly used. It uses Query Language to communicate with the database and execute the queries.

After, ORM maps itself the results to corresponding Java objects. We get the database connections from an application using the session. The session also helps to save, edit, update and retrieve the persistent object.

The instance of a session is creating with Session factory interface. We usually have just one session factory per one database server or database infrastructure. In this case, we need to create one session factory for MySQL and another one session factory for Oracle.

All ORMs can work with databases that support them. As you can see, the list is long, but you need to double-check before use. For JDBC, you need to write all code for mapping your object data to a relational model.

You have to perform all the copy process manually. Here is a code snippet:. It maps Java classes to the database tables using XML or annotations. The strengh of various "Relational Mapping" technologies is portability: you ensure your application will run on most of the ACID databases. Of course you can restrain yourself to the SQL92 standard and then do some Functional Programming or you can reuse some concepts of functionnal programming with ORM frameworks.

However, some reified concepts have no business equality an operation for instance. A common workaround relies on GUIDs which tend to upset database administrators. The session must spy relationship changes but its mapping rules push the use of collections unsuitable for the business algorithms. Then you have to implement object equality on the rich domain object acting as a key But you can't because this object has no counterpart on the business world.

So you fall back to a simple list that you have to iterate on and performance issues result from. For instance, real world web applications try to enforce session isolation by adding some "WHERE" clauses when you fetch data Then the "Session.

For instance, if your REST services use jackson library to serialize a business object. But this Jackson exactly maps to an Hibernate One. Then either you merge both and a strong coupling between your API and your database appears Or you must implement a translation and all the code you saved from the ORM is lost there It releases the constraints put on the ORM session and relies most of time on a DSL over the SQL so portability doesn't matter But on the other hand, you have to look into the transaction details, the concurrency issues.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 12 years, 1 month ago.

It is a framework,. Lazy Loading. It does not support lazy loading. Hibernate support lazy loading. Transaction management. RDBMSs represent data in a tabular format whereas object-oriented languages, such as Java or C represent it as an interconnected graph of objects.

First problem, what if we need to modify the design of our database after having developed a few pages or our application? Sometimes you will have an object model, which has more classes than the number of corresponding tables in the database.

RDBMSs do not define anything similar to Inheritance, which is a natural paradigm in object-oriented programming languages. Object-oriented languages represent associations using object references whereas an RDBMS represents an association as a foreign key column.