Regarding #1 here, I think we are looking at a defect.
a) If I start off in the data modeler and change the PK name, then FK
name is also updated.
b) If I start off in a logical model, transform to data model, then
change PK name, FK is not updated.
c) If I start off in a logical model, transform to data model, then
delete the relationship between the two tables, add it back, now
change PK name, FK is upated.
Will file a defect on this, meanwhile looks like the workaround is c).
Regarding #2, "Could the names conflict with the role names?", not
that I am aware of. Doesn't for me in some quick tests.
I created two tables, and relation between. Used same name for
a table, a role, and a column in each:
Name Type Path
buba Association Role Logical View::Schemas::S_1::NewDiagram
buba Class Logical View::Schemas::S_1::NewDiagram
buba Attribute Logical View::Schemas::S_1::buba
buba Attribute Logical View::Schemas::S_1::NewClass2
Next time you hit this, make note of the name you are trying to use then
go to Edit:Find and search on that name. Does it show up anywhere
else in the model?
Patrick Kennedy
Rational Support
On Apr 3, 8:52, Naushaba Mumtaz wrote:
> Subject: Re: (ROSE) Name space Conflicts in data modeler
> Patrick, thanks for the response.
> 1. I am not manually adding the FK columns, they have been carried down from
the class diagram as hve the associations. In the data modeler-I am only
changing the attribute names (e.g. abbreviating them, changing case etc). This
change should automatically propagate to the other tables if the attribute has
been defined as a FK there.
> To quote your example:
> Parent
> col_1 PK , If I change the name to COLUMN_1 here
>
> Child
> col_2 PK
> col_1 FK, this should automatically change to COLUMN_1 also
>
> 2. As for the name space conflicts - I am not duplicating the column names,
just changing the case and adding underscores.This name space conflict is also
happenig with the table names not just the attributes. Could the names conflict
with the role names? e.g I see there is a table called 'Layer' and also a role
name defined as '+layer'?
>
> Thanks,
> Abby
>
> ==================
> "Patrick Kennedy" <[EMAIL PROTECTED]> wrote:
> >
> >
> > >From the desription of the problem I'm guessing you are
> > manually adding the FK column from the parent into the
> > child. Basically this is a "don't do that". When you
> > have a PK and create a relation to a table, Rose will
> > automatically create a copy of the PK column(s) in the child.
> > i.e.
> >
> > If I have two tables,
> >
> > Parent
> > col_1 PK
> >
> > Child
> > col_2 PK
> >
> > then draw a relation between the two, I should wind up with,
> >
> > Parent
> > col_1 PK
> >
> > Child
> > col_2 PK
> > col_1 FK
> >
> >
> > So if you rename the PK in the parent, then it should also
> > get updated in the child.
> >
> > The error about "name space conflict" means you are trying to
> > create two columns with the same name in the same table.
> > Since the PK is automatically copied down, if you try to
> > make it directly you can run into this sort of problem.
> >
> > Patrick Kennedy
> > Rational Support
> >
> >
> > On Apr 2, 17:35, Naushaba Mumtaz wrote:
> > > Subject: (ROSE) Name space Conflicts in data modeler
> > >
> > > I have transformed a class diagram into data model using the Rose data
> > modeler add-in. I am coming up against 2 problems:
> > >
> > > 1. When I change the name of a P.K. attribute, the name change is not
carried
> > over into the other tables (e.g. where the attribute is a F.K. also). Is
there
> > a way to fix this?
> > >
> > > 2. Another error message I run into while changing the names of certain
> > attributes is 'Changing the name of this value would create a name space
> > conflict'. Why is this so and how shall I fix it?
> > >
> > > Thanks in advance.
> > >
> > > Abby
> > >
> > > __________________________________________________________________
> > > Get your own FREE, personal Netscape Webmail account today at
> > http://webmail.netscape.com/
> > > ************************************************************************
> > > * 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
> > > *
> > > *************************************************************************
> > >-- End of excerpt from Naushaba Mumtaz
> >
> >
> > ************************************************************************
> > * 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
> > *
> > *************************************************************************
> >
> >
>
> __________________________________________________________________
> Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
>-- End of excerpt from Naushaba Mumtaz
************************************************************************
* 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
*
*************************************************************************
