RE: (ROSE) Data Modeller: Object Model relations to self

[Walter Howard]

That's not so bad.  The database naming standards are certainly going to be different than the default names generated by Rose.  Even if you used ERWin, you have to do the physical model column names.  Although the foreign keys maintain the same name as the parent column names.  OTH, the incorrect implementation of generalization relationships and the generation of primary key columns is pretty annoying (It generates a 1 to many instead of a 1 to 1).  But what's really bugging me today is I added a new entity class and tried to create a new schema and Rose keeps telling me "Use the schema editor to associate this schema with a database, once a table has been added, a schema's associated database cannot be changed.".  All I did was add a new entity and now I'm dead in the water. Walter >>> Kristian Rosenvold <[EMAIL PROTECTED]> 01/11/01 08:17AM >>> Ok, it seems like I need this veeery slowly. I just defined another model with some different multiplicities. Still, none of them seem to get proper names for the foreign key for the relation to self. The "TestKey" attribute is "part of object identity". Modeller obviously understands the reference to self because the datatype of the foreign key is correct, but the names go on and on in the COLxx fashion. I know I can change the names manually in the data model, it's just such a pain. But I suppose there should be some pain in life ;) Kristian Attached is JPG of a model that I just made from scratch, in case there is any stuff left in the repository class. -----Original Message----- From: Prajesh, Jim To: Naiburg, Eric J.; Kristian Rosenvold; Gornik, Davor; [EMAIL PROTECTED] Sent: 11.01.01 14:20 Subject: RE: (ROSE) Data Modeller: Object Model relations to self The foreign key name migration works properly only when the multiplicity is defined.  If the multiplicity is not defined, the translation tool still migrates a foreign key (Not sure how it knows) but just calls the FK COL1 or something like that.  But if you have the cardinality specified then it uses the name of the primary key of the parent table.  Not sure of the reason but that is how it behaves. Eric: Would it be better if we issue a warning in the log file saying that we could not figure out how to migrate the foreign key because the multiplicity is not defined?  Just a thought. -----Original Message----- From: Naiburg, Eric J. [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 11, 2001 2:26 AM To: 'Kristian Rosenvold'; Gornik, Davor; [EMAIL PROTECTED] Subject: RE: (ROSE) Data Modeller: Object Model relations to self The foreign keys are created based on the primary key names.  You can describe the primary keys in the object model by right-click on the appropriate attribute in the browser and selecting Data Modeler --> Part of Object Identity. -----Original Message----- From: Kristian Rosenvold [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 10, 2001 5:46 AM To: 'Gornik, Davor'; [EMAIL PROTECTED] Subject: RE: (ROSE) Data Modeller: Object Model relations to self As I understand you, there is no way to influence the names of the foreign keys from the object model ? Pity ;) I thought that was what assoc/role names were all about! Kristian -----Original Message----- From: Gornik, Davor [mailto:[EMAIL PROTECTED]] Sent: 10. januar 2001 14:20 To: Kristian Rosenvold; [EMAIL PROTECTED] Subject: RE: (ROSE) Data Modeller: Object Model relations to self Kristian, You can rename the foreign key constraints to whatever you want after the generation. The conversion just uses a unique name. Same of course with the column names. Davor Gornik Marketing Engineer Rose Business Unit Rational Software      Tel: +49-89-62838-249 Keltenring 15          Fax: +49-89-62838-549 82041 Oberhaching      Cel: +49-170-4532-249 Germany                Email: [EMAIL PROTECTED] -------------------------------------------------------------------- Rational User Conference 2001 July 22 - 26,  2001 * Denver, CO, USA http://www.rational.com/ruc -----Original Message----- From: Kristian Rosenvold [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 10, 2001 11:37 AM To: [EMAIL PROTECTED] Subject: (ROSE) Data Modeller: Object Model relations to self I am trying to model a variation of a composite pattern (from Gamma et al) in Data Modeller. The generated data model is technically correct, but the names of the foreign keys (to the primary key in the same table) get very bad (on a COL_* pattern). Any ideas on how to make these more legible? As you can see from the attached jpg, I'm trying to use role/assoc names, but they don't seem to have the desired effect. This is Rose 2001, btw. <<dmquestion.jpg>> ADCORE Digital Business Creators Mobile +47 90 75 19 85 <mailto:[EMAIL PROTECTED]> ICQ: 1236925, IM: Krosenvold <<Kristian Rosenvold.vcf>> ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * ************************************************************************ * ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * ************************************************************************ *