Jean Parpaillon wrote: > Le 19.06.2006 18:29, DongInn Kim a écrit : >> Hi Jean, >> >> I finally saw your scheme. Thank you for posting your idea. :-) >> BTW, I have a question for you. >> What relation are "Package_servicelists" and "Package_rpmlists" involved >> in between "Groups" and "Packages" entities? >> In my scheme, there should not be any relationship that they can make >> from the two entities (Groups and Packages) . >> Any reason to have the two realtions (Package_servicelists and >> Package_rpmlists) betwen Groups and Packages? >> >> > In the script oscar_table.sql, I have the following: > > CREATE TABLE IF NOT EXISTS Packages_rpmlists( > ... > CONSTRAINT Packages_rpmlists_ibfk_1 FOREIGN KEY (package_id) > REFERENCES Packages (id) ON DELETE CASCADE, > CONSTRAINT Packages_rpmlists_ibfk_2 FOREIGN KEY (group_name) > REFERENCES Groups (name) ON DELETE CASCADE ON UPDATE CASCADE > )TYPE=INNODB; > > CREATE TABLE IF NOT EXISTS Packages_servicelists( > ... > CONSTRAINT Packages_servicelists_ibfk_1 FOREIGN KEY (package_id) > REFERENCES Packages (id) ON DELETE CASCADE, > CONSTRAINT Packages_servicelists_ibfk_2 FOREIGN KEY (group_name) > REFERENCES Groups (name) ON DELETE CASCADE ON UPDATE CASCADE > )TYPE=INNODB; > Oh, right. I totally forgot about this. Yes, they have relationship between Groups and Packages and I have not applied this relation to my database Entity-Relation (ER) diagram because I think the entity "Packages" and "Groups" are connected by "Group_Packages" relation and their relation (Group_Packages) is supposed to fully affect to the 6 sub packages entities (i.e., Package_rpmlists, Package_servicelists, Package_provides, .. and so on). So we don't really have to add the practical relations to the big picture of ODA scheme(i.e. ER diagram). But it is good to have the ER diagram to represent all the practical entity and relations. Thanks Jean for reminding me of this issue.
On the other hand, I think I have forgot to implement some database codes to populate the Group_Packages with the data for Package_rpmlists and Package_servicelists. I am not sure what OSCAR developers think about this but if possible, I would like to use "Group_Packages" more practically instead of messing up the database scheme (i.e., adding extra but convenient field (group_name) to Package_rpmlists and Package_servicelists). I know the current database codes work fine with the extra field of the two tables and it was easy for me to implement this too. So guys, what would you like to choose, convenience or clearness? > > Btw, for performance issues, it is not good to reference a VARCHAR > column (Groups(name)). Yes, I would like to use the CHAR type rather than VARCHAR for this case. > Furthermore, the Groups table has an 'id' column. Please refer to the following link: https://sourceforge.net/mailarchive/message.php?msg_id=15479255 Yes, we could use the 'id" column, which is the original primary key of the table"Groups" but it is somehow convenient for us to use the direct group name (which is also unique) rather than doing the sub-query to get the group name with its group_id. That's why we decided to use group_name instead of group_id. This is a contradiction of my idea about clearness :-) Regards, - DongInn > > Regards, Jean >> Regards, >> >> - DongInn >> >> Jean Parpaillon wrote: >> >>> Hi, >>> I've just uploaded a new version of the ODA relationnal outline. >>> It's on the wiki: >>> http://svn.oscar.openclustergroup.org/trac/oscar/attachment/wiki/DevODA_architecture/oscar_oda.svg >>> >>> >>> For those who have issues with svg, here it is a png version: >>> http://svn.oscar.openclustergroup.org/trac/oscar/attachment/wiki/DevODA_architecture/oscar_oda.png >>> >>> >>> >>> >>> Regards, Jean >>> >>> >>> Le 16.06.2006 17:33, Jean Parpaillon a écrit : >>> >>>> Hi, >>>> I've made an up-to-date relationnal schema of OSCAR ODA. May it be >>>> included in the trac wiki : >>>> http://svn.oscar.openclustergroup.org/trac/oscar/wiki/DevODA_architecture >>>> >>>> ? >>>> >>>> Regards, Jean >>>> > > > _______________________________________________ > Oscar-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oscar-devel > _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
