User guide

Data Integration with Sybase Avaki Studio 61
Common features of view model components
characters (including spaces, punctuation, accented characters, and so forth) are not
allowed. The name of each column in a given schema should be unique—having two
columns in the same schema with the same name can cause Studio difficulty when try-
ing to access the columns by name.
Note If your schema has column names that do not conform to these norms, you
must use the methods in the ResultSet object to access them by position (using a
1-based index). We suggest setting up your database operations to alias any col-
umns with questionable names so that they are not confusing within Studio.
Type. The data types of your columns correspond to common SQL types of the same
name. The types available within Studio are ARRAY, BIGINT, BINARY, BIT, BOOL-
EAN, BLOB, CHAR, CLOB, DATE, DECIMAL, DISTINCT, DOUBLE, FLOAT, INTEGER,
JAVA_OBJECT, LONGVARBINARY, LONGVARCHAR, NULL, NUMERIC, OTHER,
REAL, REF, SMALLINT, STRUCT, TIME, TIMESTAMP, TINYINT, VARBINARY, VAR-
CHAR,
and ORACLE_CURSOR. For information about these types, consult any SQL
reference.
Advanced Studio users will note that the standard JDBC type mappings are used to
construct the Java representations of the column values that they can manipulate in
Studio. For information about the Java types to which these map, refer to the Sun
JDBC documentation:
http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/map
ping.html#996857