visualises the aforementioned mappi

visualises the aforementioned mapping example. The boxes contain the types declared inside the scope of J% (Java
types) and SQL. We declare types in the Java type system, which have a one-to-one relation with the correspondent SQL types.
Then, we associate them with the Java types marked as “mapped” to provide the mapping information and conversion
functions. The arrowheads illustrate the conventions that are used.
Table 4 lists all the compatible and dominant types for the SQL module. So far, the module supports on MySQL data types.1
Each database backend should have its own custom type mapping rules, since it is common for RDBMS's to have unique data
types. The types listed on the table provide the basic mapping between Java and MySQL. SQL sets and Java collections and
composite types are also supported (see Section 4.6).

ผลลัพธ์ (อังกฤษ) 2:

visualises the aforementioned mapping example. Boxes contain the scope of the types DECLARED Inside the J% (Java
types) and SQL. We Declare types in the Java Type System, which have a one-to-one relation with the Correspondent SQL types.
Then, we Associate them with the Java types marked as "mapped" to provide the information Mapping and conversion
functions. The arrowheads illustrate the Conventions that are used.
Table 4 lists all the Dominant Compatible and types for the SQL Module. So Far, the Module Data Types.1 SUPPORTS on MySQL
Database backend Each should have ITS own Custom Type Mapping Rules, since it is common to have for RDBMS's Unique Data
types. The types listed on the table provide the basic mapping between Java and MySQL. SQL and Java Collections sets and
composite types are also supported (See Section 4.6).