Hi!
1. nextgen_EnterpriseEntity is created fine for the first time. At each
successive start JAWS tries to create it again but fails, as teh table
already exists. Is this the intended behavior ?

2. The real troublemaker is nextgen_EntityPK.
The statement for creation reads:
CREATE TABLE nextgen_EntityPK (otherField INTEGER,anInt INTEGER,aDouble
DOUBLE,aBoolean BIT,aString VARCHAR(256),aLong BIGINT)

This fails because Interbase is not capable of the followings types:
BIT, BIGINT, DOUBLE

In the documentation I found the following mapping instructions:

-----

JDBC to InterBase Native Type Mapping

Mapping from JDBC types to the preferred InterBase and Java types.
The driver converts between types according to the JDBC specification.

 JDBC Type NameInterBase Type Name           Java Type Name
 CHAR(n)       CHAR(n) see note 1            java.lang.String
 VARCHAR(n)    VARCHAR(n) see note 1         java.lang.String
 LONGVARCHAR   BLOB SUB_TYPE TEXT see note 1 String or
java.io.InputStream
 BINARY(n)     CHAR(n) CHARACTER SET BINARY  byte[]

 VARBINARY(n)  VARCHAR(n) CHARACTER SET      byte[]
               BINARY
 LONGVARBINARY BLOB SUB_TYPE 0               byte[] or
java.io.InputStream
 DATE          DATE see note 2               java.sql.Date
 TIME          DATE see note 2               java.sql.Time
 TIMESTAMP     DATE see note 2               java.sql.Timestamp
 SMALLINT      SMALLINT                      short
 INTEGER       INTEGER                       int
 REAL          FLOAT                         float
 DOUBLE        DOUBLE PRECISION              double
 NUMERIC(p,s)  NUMERIC(p,s)                  java.math.BigDecimal
 DECIMAL(p,s)  DECIMAL(p,s)                  java.math.BigDecimal
 OTHER         ARRAY see note 3              java.lang.Object

Note 1: See Character Set Support.

Note 2: An InterBase DATE stores both date and time down to the number
of
seconds since Jan 1, 100 AD. The precision stored is actually 10,000th
of a
second but sub-second times are not currently supported by InterClient.

Note 3: InterBase arrays are currently treated as binary blob data.
Future
releases of InterClient will add support for InterBase arrays as an
extension to the JDBC API.

-----

I could setup a jaws.xml file now. But what to do with it ? I couldn't
find a jaws.xml or jboss.xml file in TestBeans.jar.

Thanks,
Tobias

marc fleury wrote:
> 
> > [JAWS] java.lang.reflect.InvocationTargetException:
> > interbase.interclient.SQLException: [interclient][interbase] Dynamic SQL
> > Error
> > [JAWS] SQL error code = -204
> > [JAWS] Table unknown
> > [JAWS] NEXTGEN_ENTITYPK
> 
> It seems the table is never created.  This means that jaws w/ interbase
> chokes on one of the fields of the Primary key at creation time (boolean,
> int, long, double, String), try to look for the stack trace of startup and
> tell me what the server says at deployment time when it tries to create the
> schema...
> 
> And your other tables create fine, yes? (field-CMP and BMP) (obviously since
> you run to 77 :(
> 
> marc


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to