The document discusses 5 different types of JDBC drivers that can be used to connect to a database including Type 1 (JDBC-ODBC bridge), Type 2 (Native-API, partial Java), Type 3 (Native-API, 100% Java), Type 4 (Native Protocol), and Type 5 (Native-Protocol, indirect access via JNDI). It provides details on how each type of driver works, including whether it uses native calls or converts to network protocols, and examples of common class names used for each type. The document also covers database metadata and how result sets, statements, and connections interact with JDBC drivers.
The document discusses 5 different types of JDBC drivers that can be used to connect to a database including Type 1 (JDBC-ODBC bridge), Type 2 (Native-API, partial Java), Type 3 (Native-API, 100% Java), Type 4 (Native Protocol), and Type 5 (Native-Protocol, indirect access via JNDI). It provides details on how each type of driver works, including whether it uses native calls or converts to network protocols, and examples of common class names used for each type. The document also covers database metadata and how result sets, statements, and connections interact with JDBC drivers.
The document discusses 5 different types of JDBC drivers that can be used to connect to a database including Type 1 (JDBC-ODBC bridge), Type 2 (Native-API, partial Java), Type 3 (Native-API, 100% Java), Type 4 (Native Protocol), and Type 5 (Native-Protocol, indirect access via JNDI). It provides details on how each type of driver works, including whether it uses native calls or converts to network protocols, and examples of common class names used for each type. The document also covers database metadata and how result sets, statements, and connections interact with JDBC drivers.
The document discusses 5 different types of JDBC drivers that can be used to connect to a database including Type 1 (JDBC-ODBC bridge), Type 2 (Native-API, partial Java), Type 3 (Native-API, 100% Java), Type 4 (Native Protocol), and Type 5 (Native-Protocol, indirect access via JNDI). It provides details on how each type of driver works, including whether it uses native calls or converts to network protocols, and examples of common class names used for each type. The document also covers database metadata and how result sets, statements, and connections interact with JDBC drivers.
Bhdae (wriHen in ) 7pe 2 Natre API ath Jara ) Tyne AI JAr e t hoBe tel Jara) yne 4 Native yotoul Ai Javs) Dves 9anag es Stati c Connecion geY Connehn (5tin URL) 5Aahc Connee kar 9et (onnechen ting VRL, Stin Result Set VL7-name ing Me thods E o t tof-emoy n45%lwor) object gefRRTES*t () getRou () ,9et5tint) objeut. pt alumnount( ) gct nt Naive A ODn AP is (onver u API Calls ative NahveNaHve Paatocal DBC call s Are Convertrd to Net worK rotoco| Typel lass for Narne sunjdb. odb Dwa Manager. 9et bcodbeDiven" yne2 Class or Nane (hlonnedion j4be edhe : o7g DE_NHME 9veranayur. CinnetH»n apa the derdy Jabe. t CliWe 'abe ne Class forN ame C" mysql jdbc. Privet') cem derby :l localhosh: entdsive*) 02acle lO Deivesan ay ge Corne ehen ( Jdbu: ms . Tpsdb lota lhot Ds 6tvdn ); Tyne Cla5s.for Name ( 01 acle 1db t. diveT . OtarleD-ivar " Jj Priv&T anag er. qd (onnut on 7" jdbuOTaule: thin: neol 1ga1 44
KosultSe tMeta Date Paar of
Database MetaDeta ResultSet Tntrface fart of (OnnectioGn Totersace getUserName () isRe ad 0a ly y Gtat ement Intrfue
frpared 5* atem tn
olable 5katement Caable 5+atemeil 1
CallableState meat clbstmt Con. nrenare (al
Call tots| Srak") i
Conn ection Symta« otoce Subrotoco datasovfte name