web server - Borland Technical Publications

Setting Properties
databases (except for JDataStore) if you specify the dialect, then the Container
automatically creates tables for container-managed entities for you. The Container will
not create these tables unless you specify the dialect.
However, the Container can detect the dialect from the URL for the JDataStore
database. Thus, for JDataStore, the Container will create these tables regardless of
whether you explicitly specify the dialect.
The following table shows the names or values for the different dialects (case is
ignored for these values):
Database Name
JDataStore
Oracle
Sybase
MSSQLServer
DB2
Interbase
Informix
No database
Dialect Value
jdatastore
oracle
sybase
mssqlserver
db2
interbase
informix
none
Mapping Java types to SQL types
When you develop an enterprise bean for an existing database, you must map the SQL
data types specified in the database schema to Java programming language data
types.
The Borland EJB Container follows the JDBC rules for mapping Java programming
language types to SQL types. JDBC defines a set of generic SQL type identifiers that
represent the most commonly used SQL types. You must use these default JDBC
mapping rules when you develop an enterprise bean to model an existing database
table. (These types are defined in the class java.sql.Types.)
The following table shows the default SQL to Java type mapping as defined by the
JDBC specification.
Java type
boolean/Boolean
byte/Byte
char/Character
double/Double
float/Float
int/Integer
long/Long
short/Short
String
java.math.BigDecimal
byte[]
java.sql.Date
java.sql.Time
java.sql.Timestamp
java.util.Date
java.io.Serializable
JDBC SQL type
BIT
TINYINT
CHAR(1)
DOUBLE
REAL
INTEGER
BIGINT
SMALLINT
VARCHAR
NUMERIC
VARBINARY
DATE
TIME
TIMESTAMP
TIMESTAMP
VARBINARY
Chapter 14: Entity Beans and CMP 1.1 in Borland Enterprise Server 123