You can also turn off autocreate, and create your tables outside
orion. This gives you access to foreign keys and referential integrity
checking, indexes, etc.
Kirk Yarina
At 09:36 AM 3/9/01 -0500, you wrote:
>Hello, Christian:
>I have an application which has a lot of one-to-many EJB-to-dependents
>relationships. What I have experienced is that you can define data-type in
>your deployment descriptor "orion-ejb-jar.xml", including redefining field
>size to whatever you expect, instead of having all string fields to be
>varchar2(255) from Orion creation. This means you can use
>"persistence-type="xxx(xxx)"" right after <cmp-field-mapping name="xxx"> to
>define your key size.
>Good luck!
>
>
>
>Ruth He
>
>Canlink Interactive Technologies
>303 Bagot Street
>Kingston, ON, Canada
>K7K 5W7
>
>http://www.canlink.com
>Phone: 613-549-7883
>Email: [EMAIL PROTECTED]
>
>----- Original Message -----
>From: Christian Billen <[EMAIL PROTECTED]>
>To: Orion-Interest <[EMAIL PROTECTED]>
>Sent: Thursday, March 08, 2001 2:05 PM
>Subject: Dependent Primary Key
>
>
> > Hi list,
> >
> > I realize the very existence of Dependent might be changing in the near
> > future, but have some question regarding their use in the current
> > implentation on orion 1.4.7
> >
> > I have a Person (EJB CMP) with a one-to-many PhoneNumber(dependent). My
> > problem is that orion creates a person_phonenumbers table and try to make
>a
> > composite primary key with all the fields in my PhoneNumber. It does
>cause
> > a problem as my database has a limit on the size of the key.
> > Is there a way to specify what the primary key for a dependent should be
>so
> > that the autocreate table can do it properly or should I create my table
> > ahead of time to the spec I want ?
> >
> > Thanks,
> >
> > Christian
> >
> >
> >
