翻译文献Understanding the ORAData Interface.docVIP

大连交通大学2016届本科生毕业设计（论文）外文翻译  PAGE - 39 - 外文原文 Understanding the ORAData Interface One of the choices in making an Oracle object and its attribute data available to Java applications is to create a custom object class that implements the oracle.sql.ORAData and oracle.sql.ORADataFactory interfaces (or you can implement ORADataFactory in a separate class). The ORAData and ORADataFactory interfaces are supplied by Oracle and are not a part of the JDBC standard. Understanding ORAData Features The ORAData interface has these advantages:
It recognizes Oracle extensions to the JDBC; ORAData uses oracle.sql.Datum types directly.
It does not require a type map to specify the names of the Java custom classes you want to create.
It provides better performance: ORAData works directly with Datum types, the internal format the driver uses to hold Oracle objects. The ORAData and ORADataFactory interfaces do the following:
The toDatum() method of the ORAData class transforms the data into an oracle.sql.* representation.
ORADataFactory specifies a create() method equivalent to a constructor for your custom object class. It creates and returns a ORAData instance. The JDBC driver uses the create() method to return an instance of the custom object class to your Java application or applet. It takes as input an oracle.sql.Datum object and an integer indicating the corresponding SQL typecode as specified in the OracleTypes class. ORAData and ORADataFactory have the following definitions: public interface ORAData { Datum toDatum (OracleConnection conn) throws SQLException; } public interface ORADataFactory Note: The JPublisher utility supports the generation of classes that implement the ORAData and ORADataFactory interfaces. See Using JPublisher to Create Custom Object Classes on 45. { ORAData create (Datum d, int sql_Type_Code) throws SQLException; } Where conn represents the Connection object, d represents an object of type oracle.sql.Datum, and sql_Type_Code represents the S