Where are the JDBC types in the table editor of Java Dictionary?
Actually, in Java Dictionary you do not work with JDBC types. Rather, you work with pre-defined types called built-in types (for example, “integer,” “float,” “timestamp,” “string”). The built-in types map to the standard JDBC types. Why is this indirection necessary? Well, for example, there are some differences in the semantics of the JDBC types across the supported DBMS. The built-in types eliminate this drawback: They are proven to behave identical on each supported DBMS platform. Your data domain is ready to run immediately on each supported DBMS. Back to top As I have read in the documentation, Open SQL for Java defines the default mapping between Java Dictionary build-in data types and JDBC data types. If so, why does Java Dictionary define its own types instead of working with JDBC types directly? First, there are some differences in the semantics of the JDBC types across the supported DBMS. An example here is the handling of strings independent of their length (JDBC types VARCH
