كيف تتحدث Java مع قاعدة البيانات

Written Explanation

What JDBC is

JDBC (Java Database Connectivity) is the standard Java API for working with relational databases. It lets a Java program connect to a database, send SQL, and read the results. Oracle's Java tutorial describes it as covering connections, statements, result sets, and transactions, all in the java.sql package that ships with the JDK.

Notice what JDBC is not: it is not a database, and it does not know PostgreSQL's wire format. It is a set of types and method names. Someone still has to do the real talking.

The driver does the real talking

A driver is a library that implements the JDBC types for one particular database. It translates a call such as "run this SQL" into the network protocol that database understands. PostgreSQL has its own driver, the PostgreSQL JDBC Driver (often called pgjdbc). A MySQL driver speaks MySQL's protocol instead.

 Your Java code
      |   uses Connection, PreparedStatement, ResultSet   (JDBC API, java.sql)
      v
 PostgreSQL driver   (org.postgresql.Driver, a jar on your classpath)
      |   speaks PostgreSQL's network protocol
      v
 PostgreSQL server   (the library with the shelves)

The librarian analogy: JDBC is the shape of the conversation (dial, ask, listen, hang up). The driver is the phone line to one specific library. Change the library and you change the line, but you still dial, ask, listen, and hang up the same way.

The three types you will use all module

All three are interfaces in java.sql. Your code is written against the interfaces. The driver supplies the real classes behind them, so your code never names a PostgreSQL class (you will see that in Example 1). You met this idea in BEG-024: programming to an interface lets you swap the implementation.

The flow, in five steps

Almost every database call in Java follows the same order:

1. Connect: open a Connection (lesson 2).
2. Prepare: create a PreparedStatement from SQL text with ? placeholders (lesson 3).
3. Execute: run it. executeQuery() for a SELECT, executeUpdate() for an INSERT, UPDATE, or DELETE.
4. Read: walk the ResultSet row by row, or read the number of changed rows.
5. Close: release the ResultSet, statement, and connection. Try-with-resources from BEG-029 does this for you.

How the driver gets found

With a modern driver you do not have to register anything by hand. DriverManager, the JDK class that opens connections, loads every driver it finds on the classpath through Java's service-provider mechanism. Adding the driver jar is enough. The PostgreSQL JDBC documentation says that for Java 1.6 and later the driver loads automatically; explicit Class.forName("org.postgresql.Driver") lines in old tutorials are a leftover from older setups.

When you later call DriverManager.getConnection(url, ...), the URL starts with jdbc:postgresql: and tells DriverManager which driver should handle it.

Adding the driver with Maven

The driver is an ordinary library on Maven Central. You add it as a dependency, exactly as you learned in BEG-054:

<dependency>
  <groupId>org.postgresql</groupId>
  <artifactId>postgresql</artifactId>
  <version>42.7.8</version>
</dependency>

The version above is the one used while writing this lesson. Check Maven Central for the current release when you start your own project, and keep the version in one place in your pom.xml.

Where JDBC sits in your career path

JDBC is the foundation under almost every Java persistence tool. Frameworks you will meet later (connection pools, Spring, JPA) call these same interfaces underneath. Learning raw JDBC now is like learning to drive a manual car: you will understand what the automatic one does for you. A later module in the roadmap, JNR-025, builds on this one with connection management and batching.