RE: Can't deploy example "atm" with datasource "db2" (NOW I CAN DEPLOY)

2000-06-15 Thread Matthias_Weiler 

That' s OK. Thank you Joe.

Matthias


-- Weitergeleitet von Matthias Weiler/AVSG on
15.06.2000 09:24 ---


"Joe Walnes" <[EMAIL PROTECTED]>@orionserver.com on 14.06.2000 18:02:11

Gesendet von:  [EMAIL PROTECTED]


An:   Orion-Interest <[EMAIL PROTECTED]>
Kopie:
Thema:RE: Can't deploy example "atm" with datasource "db2"


> In the database-schemes the "type" is the Java-Class and the "name" is
the
> Column-Type in the database.
> So the entry for name should be name="long varchar", but what is the
entry
> for type ?

java.io.Serializable

-Joe Walnes

RE: Can't deploy example "atm" with datasource "db2"

2000-06-14 Thread Matthias_Weiler 

Hi Esa, Hi Joe !

Thank you for the quick reponse, but my question was not so exactly. Sorry.

I know database-schemes. The field "value" is generated for the serialized
"LogEntryBeans" from orion.

In the database-schemes the "type" is the Java-Class and the "name" is the
Column-Type in the database.
So the entry for name should be name="long varchar", but what is the entry
for type ?

Matthias

Here is my database-scheme:


http://www.orionserver.com/dtds/database-schemas.dtd">

Can't deploy example "atm" with datasource "db2"

2000-06-14 Thread Matthias_Weiler 

If I deploy the example "atm" I get the following error:

>>
Auto-deploying atm...
Auto-deploying atm-ejb.jar...
Auto-creating table: create table acme_atm_ejb_Account_log (id varchar (255) not null, 
value longvarbinary)
Warning: Error creating table: [IBM][CLI Driver][DB2/NT] SQL0204N  "LONGVARBINARY" ist 
ein nicht definierter Name.  SQLSTATE=42704

done.
<

How can I change the type-mapping from longvarbinary to longvarchar for the LogEntries 
?


Matthias