Re: Database column creation order when using compound keys

[Markus Holmberg]

If you specify the column names (and order) in your insert statement it
won't matter in which order Orion created the columns.

Markus

On Mon, May 14, 2001 at 03:41:03PM +, Erwin Teseling wrote:
 Hello everybody,
 
 I am having some problems regarding the order in which Orion creates the 
 database columns for compound keys for an entity bean when using CMP. 
 
 I have an entity bean that models a many-to-many relationship, which has 
 a compound key (subscriptionID  userID). Now when creating the database 
 tables Orion seems to be inconsistent on the order in which these two are 
 mapped on the database table. On one machine subscriptionID is mapped on 
 the first column and on another machine (or at another time) userID is 
 mapped on the first column (and subscriptionID on the second). 
 
 Now when I fill my database with a very simple SQL script sometimes my 
 data gets mixed up because it fills the wrong column with the wrong data. 
 Offcourse I can fixs this in the script, but is there a way to tell Orion 
 which field should mapp to which column in the columns to be created in 
 the database??
 
 Thanks!
 
 Regards,
 Erwin Teseling

-- 

Markus Holmberg |   Give me Unix or give me a typewriter.
[EMAIL PROTECTED]  |   http://www.freebsd.org/

RE: Database column creation order when using compound keys

[Jeff Schnitzer]

The order should be determined by the elements in the orion-ejb-jar.xml
deployment descriptor.

Unfortunately there is a bug in 1.4.5 which causes the order of compound
PK fields to switch on every deployment.  It was fixed in 1.4.6.  See
bug #242.

There is another similar problem in 1.4.8 which my test project
discovered, but my normal application works fine, so I haven't spent a
lot of time worrying about it :-)  Take a look at bug #413.

Jeff

 -Original Message-
 From: Erwin Teseling [mailto:[EMAIL PROTECTED]]
 Sent: Monday, May 14, 2001 8:41 AM
 To: Orion-Interest
 Subject: Database column creation order when using compound keys
 
 
 Hello everybody,
 
 I am having some problems regarding the order in which Orion 
 creates the 
 database columns for compound keys for an entity bean when using CMP. 
 
 I have an entity bean that models a many-to-many 
 relationship, which has 
 a compound key (subscriptionID  userID). Now when creating 
 the database 
 tables Orion seems to be inconsistent on the order in which 
 these two are 
 mapped on the database table. On one machine subscriptionID 
 is mapped on 
 the first column and on another machine (or at another time) 
 userID is 
 mapped on the first column (and subscriptionID on the second). 
 
 Now when I fill my database with a very simple SQL script 
 sometimes my 
 data gets mixed up because it fills the wrong column with the 
 wrong data. 
 Offcourse I can fixs this in the script, but is there a way 
 to tell Orion 
 which field should mapp to which column in the columns to be 
 created in 
 the database??
 
 Thanks!
 
 Regards,
 Erwin Teseling