0
This is where you have two tables and each record on one table has one and only one corresponding record on the other. To connect them, they both have a corresponding code, that is unique in each table. So you could have a database for employees. In a table in it you could have all their personal details. On another you could have their salary details. On both tables, for each individual there would be a unique code, like an employee code. When a particular employee is found on the employee table, their code is taken and checked for on the salary table to find the details for their salary. It is then not necessary to have their name in both tables, as the code can be used to link the two parts of their data together from the two tables. The code is the only thing that will be in both tables. As every code on one table has one corresponding code on the other it is a one to one relationship. There are other types of database relationships, namely one to many and many to many.
Wiki User
∙ 15y ago
Add your answer:
Earn +20 pts
Can a relational database support one to one?
Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.Yes. A one to one relationship is one of the types of relationships a relational database can have.
A schematic of the entire database that describes the relationships in a database is called?
entity-relationship diagram.
What is a logical database?
A logical database is the structure of data. It is the different pieces of information and the relationships between them.
Which database tool is required for establishing relationships?
tables
What is a Configuration Management Database?
A Configuration Management Database (CMDB) stores configuration records containing Attributes of CIs and their relationships. A CMS may include one or more CMDBs.
What are the Different types of relationship in a database?
There are mainly three types of relationships in database . These are One to One , One to Many , Many to Many. One to one relationship can be seen as relationship between husband and wife , one to many relationship can be seen as a relationship between a college and students.
What is an Entity Relationship diagram for library management database?
An entity relationship diagram is a graphical documentation of a database's tables, fields, and the relationships between tables in the database. It shows all of the fields in each of the tables, and sometimes describes the data types for those fields as well as having lines between the tables that show relationships. The relationships can be one-to-many, or one-to-one relationships. A one-to-many (the most common) relationship means that one row in one of the tables will relate directly to many rows in the other table (hence the reason the data is in two tables.) One-to-one relationships are use to separate data that could be located in the same table as the other data into multiple tables.Entity relationship diagrams are helpful when querying a database as well to understand how to write the SQL to pull the data out of the database. These diagrams are useful to database designers, database administrators, computer programmers, and database users to understand the structure of the database.------------------------------------------------------------------------------------------------------------------hiii i m mehul, frnds m giving a er diagram for library management, ok..check out here, its gud..http://www.kdd.uncc.edu/Cynthia/3160Proj/Report_Final.pdfand this has all dfds, erds, class diagrams n all..http://www.docstoc.com/docs/9375857/library-mangment-system-anlysis-anddesginhave a bright carrier-------------------------------------------------------------------------------------------------------------------
What is a one-to-many relationship?
It is a term from computer databases. A relational database can have a one-to-many relationship in its data. For example, if you have a customer order database, one table will contain customer names and another will contain their orders. Each customer will only be listed once, but each customer can make many orders. So one customer can be related to many orders. Incorporating that into a database requires the creation of a one to many relationship.
What is network model in DBMS?
network model is a collection data in which records are physically linked through linked lists .A DBMS is said to be a Network DBMS if the relationships among data in the database are of type many-to-many. The relationships among many-to-many appears in the form of a network. Thus the structure of a network database is extremely complicated because of these many-to-many relationships in which one record can be used as a key of the entire database. A network database is structured in the form of a graph that is also a data structure .
Difference between database and relational database?
A database is a collection of data organized for easy access and manipulation, while a relational database is a type of database that stores data in a structured format using tables that are related to each other through keys. In a relational database, data is organized into rows and columns, and relationships between tables can be established using keys.
Which one of the following diagrams is the most helpful in designing a relational database in which to store object data?
The Entity-Relationship diagram is the most helpful in designing a relational database to store object data. It visually represents entities, their attributes, and the relationships between them, providing a clear understanding of the database structure and enabling effective planning of tables and relationships.
How do you find relation between tables in a database?
There are two generic types of relationships that are found between tables in existing databases, those that are explicit (or defined) and those that are implicit (or undefined.) The explicit relationships are defined differently in each database management system, so finding these relationships will depend on which type of database you're using. Typically they can be found via the user interface when designing one of the two tables in the relationship, viewing a relationship option, or by applying SQL against specific system tables. The explicit relationships usually enforce referential integrity in the database, so they are strongly encouraged over implicit relationships, but still implicit relationships will be found in the real world in existing databases. Implicit relationships are relationships where the primary key in one table can be clearly identified in another table as a foreign key, but there is no explicit relationship defined. Because the name of the foreign key matches or is similar in pattern to the the the primary key in the other table, you can imply that there should be a relationship between those tables. These relationships can be identified by foreign key names and by looking at existing SQL and queries in the database system to see what fields tables are joined on.
