ODBC and JDBC Guide

Chapter 7 | Reference information 30
String length is optional in table declarations. All strings are stored and retrieved in Unicode.
Note FileMaker repeating fields are supported like arrays.
Example
Mapping FileMaker fields to JDBC data types
The JDBC client driver uses the following mappings when converting FileMaker data types to
JDBC SQL types.
The JDBC client driver converts the FileMaker calculation data type to the JDBC SQL type
matching the calculation’s result. For example, the JDBC client driver converts a FileMaker
calculation that results in a timestamp data type to java.sql.Types.TIMESTAMP.
Data types in 64-bit applications
In the 32-bit version of the ODBC API, some functions used parameters that could pass integer
values or pointer values, depending on context. But in 64-bit Windows operating systems, integers
and pointers are not the same size. The 64-bit version of the ODBC API uses abstract data types
that are not defined as a specific size.
Applications that use 32-bit values may crash when they are ported to a 64-bit operating system.
Applications that use abstract data types work correctly on both 32-bit and 64-bit operating
systems.
ODBC and JDBC error messages
Here are the basic formats of error messages you receive when working with FileMaker and
ODBC/JDBC.
ODBC error messages
Error messages can come from:
1 ODBC driver errors
1 FileMaker and FileMaker XDBC Listener errors
INSERT INTO mytable(repField[3]) VALUES (‘this is rep 3’)
SELECT repField[1], repField[2] FROM mytable
FileMaker field type Converts to JDBC SQL type
text java.sql.Types.VARCHAR
number java.sql.Types.DOUBLE
date java.sql.Types.DATE
time java.sql.Types.TIME
timestamp java.sql.Types.TIMESTAMP
container java.sql.Types.BLOB
calculation specified by the data type of the calculation’s result