Thanks for the replies. Just to confirm. If you guys were creating the database of this model:
http://imagebin.org/158118 Would Not want a Wt::Dbo::ManyToMany relationship; But would use two Wt::Dbo::ManyToOne relations, right? That way I can create table 'users_has_projects' with 2 attributes and work with them without problems, right? Tks again, John ps: pardon the redundancy, DB is a very important part of the project. On 05/31/2011 05:59 PM, Dmitriy Igrishin wrote: > Strictly speaking, the join table does not represents a class of entities. > But only entity can contains attributes. Therefore, in you case, > "users_and_projects" must be considered as entity rather than the join table > (which always serves only as an implementation detail on the physical, i.e. > the database level, while entities are always should be considered on > logical, > i.e. the project level) because it contains attributes. > > PS, consider to rename "users" to "user" and "projects" to "project" > according to classical entity-relationship models, because > the terms "one-to-many" or "many-to-many" are meaningless > if entities are named in plural. Tks, what is the correct way? ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
