Solved

Entity relation

Posted on 1998-09-24
1
577 Views
Last Modified: 2008-03-06
Are weak entities necessary?  What is the distinction between a weak entity and a strong one?  Can a weak entity be converted to a strong entity?
0
Comment
Question by:hemag
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 3

Accepted Solution

by:
junfeb earned 10 total points
ID: 1025749

A weak entity (``W'') is a component of an entity-relationship diagram that has all the characteristics of an entity, except that there is no set of attributes of the
weak entity that forms a key, and such that there is an entity (or another weak entity) E, such that

     every instance of W is associated with exactly one instance of E,
     a ``primary key'' for the weak entity W can be obtained from the primary key for E by including one or more of the attributes of W.

Thus the primary key of a weak entity is not a subset of (just) the set of the weak entity's attributes; it includes attributes from another entity as well (or, maybe
even several other entities, if this weak entity is associated to another weak entity).

Note, by the way, that this definition does not imply that each instance of the ``strong'' entity E must have an instance of W associated to it. In fact, an instance
of E could have zero, one, or even many instances of W associated to it.

 you should use a weak entity when you would use a (regular) entity, but you find that a key can't be formed from the available attributes, and when each instance of the new weak entity is associated with - or depends on - exactly one instance of some entity.

0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
This article explains all about SQL Server Piecemeal Restore with examples in step by step manner.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question