JDBC 3.0 versus JDBC 4.0
Revise as diferencas entre JDBC 3.0 e JDBC 4.0 em uma tabela estruturada e depois continue com perguntas de entrevista, testes e comparacoes semelhantes.
Diferenca entre
JDBC 3.0 vs JDBC 4.0 - uma comparacao importante de temas que ajudara voce a entender qual e melhor para o seu caso. Confira a comparacao de JDBC 4.0 e JDBC 3.0 como perguntas comuns de entrevista.
Diferenca entre JDBC 3.0 e JDBC 4.0
JDBC 3.0 vs JDBC 4.0 - uma comparacao importante de temas que ajudara voce a entender qual e melhor para o seu caso. Confira a comparacao de JDBC 4.0 e JDBC 3.0 como perguntas comuns de entrevista.
|
JDBC 3.0
|
JDBC 4.0
|
|---|---|
| Features: - Reusabilty of prepared statements by connection pools. - In this version there is number of properties defined for the ConnectionPoolDataSource. These properties can be used to describe how the PooledConnection objects created by DataSource objects should be pooled. - A new concept has been added to this API is of savepoints: One of the useful new features is transactional savepoints. With JDBC 3.0, the transactional model is now more flexible. - Retrieval of parameter metadata. - It has added a means of retrieving values from columns containing automatically generated values. - Added a new data type i.e. java.sql.BOOLEAN. - Passing parameters to CallableStatement. - The data in the Blob and Clob can be altered: JDBC 3.0 introduces a standard mechanism for updating BLOB and CLOB data. - DatabaseMetaData API has been added. - It allows stored procedure parameters to be called by name. |
Features: - Auto- loading of JDBC driver class: In JDBC 4 invoking the getConnection() on DriverManager will automatically load a driver. - Connection management enhancements: In jdbc it may happen that a Connection is lying idle or not closed in a pool, then it became stale over time. This will led to the connection pool run out of resources due to stale connection. - Support for RowId data type: JDBC introduces support for ROWID, a data type that had been in use in database products even before it became part of the SQL. - SQL exception handling enhancements: JDBC 4 addresses the error handling beautifully. As databases are often remotely accessible resources, problems such as network failures is common and it can cause exceptions when executing a database operation. SQL statements can also cause exceptions. Prior to JDBC 4, most JDBC operations generated a simple SQLException. - SQL XML support. - DataSet implementation of SQL using Annotations: The JDBC 4.0 specification leverages annotations to allow developers to associate a SQL query with a Java class without a need to write a lot of code to achieve this association. |
Salvar para revisao
Adicione este item aos favoritos, marque-o como dificil ou coloque-o em um conjunto de revisao.
Faca login para salvar favoritos, perguntas dificeis e conjuntos de revisao.
Diferencas relacionadas
Explore comparacoes semelhantes ligadas a JDBC 3.0 e JDBC 4.0 para obter mais contexto e melhorar a preparacao para entrevistas.
Veja as diferencas abaixo
Explore todas as comparacoes disponiveis abaixo ou use a busca acima para filtrar a lista instantaneamente.