0.8.5 (URL is still http://www.orionserver.com/new/orion0.8.4c.zip) contains
support for database-schemas which will make this easier to fix (also comes
with a sybase schema in the core). A "quick fix" in your current version if
you
dont want to upgrade is to change the peristence type of the key from "id"
to
"id not null" though.
0.9.0 (the next "official" version, 0.8.5 isnt official due to lack of docs)
will
also support other nice stuff like for instance full Object<->Relational
mapping
support among other things though and is due any day now so you might want
to wait with the upgrade (since a reconfiguration of the system can be
cumbersome),
that's your call.
Have a nice day!
/Magnus Stenman, the Orion team
----- Original Message -----
From: "Philippe Renon" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Friday, January 28, 2000 6:13 PM
Subject: Orion 0.8.2 & Sybase 11.9.2
> > Hi,
> >
> > I just started playing around with Orion and it looks great, but when I
> > enabled the new-app I got the following error:
> >
> > Auto-creating table: create table com_evermind_ejb_NewsItem (id
> > INTEGER primary key, subject VARCHAR (255), text VARCHAR (255), date
> > datetime, submitter VARCHAR (255), locale VARCHAR (5))
> > Warning: Error creating table: A column in a primary key
> > constraint's column list is not constrained to be not null, column name:
> > 'id'.
> >
> > I also got this error:
> > Warning: Error creating table: Can't find type 'TIMESTAMP'.
> > but got around it by changing the "TIMESTAMP" to a "datetime".
> >
> > I'm running Orion against Sybase 11.9.2 on Solaris.
> >
> > Does anyone know how to fix this? Do I have to change some setting in
> > Sybase?
> >
> > Philippe.
> >
> >
> > PS: In the mailing list archive I saw a message mentionning Orion 0.8.3
> > but the site only offers 0.8.2 for download. Is Orion 0.8.3 for VIPs
only
> > ;-)
