The three methods of retrieving data from multiple tables are quite distinct from one another and, as a rule, perform different kinds of retrieval tasks. Because joining and subquerying both involve merging streams of data from rows in different tables, their roles overlap under some conditions. A correlated subquery, which can form a relational linkage with columns in the main table, can sometimes enable a set specification to produce the same output as a join, without the use of a join. Union queries, on the other hand, do not merge streams; rather, they “stack” rows. Their role never overlaps with those of joining queries or subqueries.
Joins, subqueries, and unions are not mutually exclusive, although union sets cannot be joined to one another or to other sets. Joined and union set specifications can include subqueries, and some subqueries can contain joins.
Joining is one of the most powerful features of a relational database because of its capacity to retrieve abstract, normalized data from storage and deliver denormalized sets to applications in context. In JOIN operations, two or more related tables are combined by linking related columns in each table. Through these linkages, a virtual table is generated that contains columns from all of the tables.
Join operations produce read-only sets that cannot be targeted for INSERT, UPDATE, or DELETE operations. Some application interface layers implement ways to make joined sets behave as if they were updatable.
A subquery is a SELECT statement that is embedded within another query. Embedded query in-line query, nested query, and sub-select are all synonyms for subquery. They are used under a variety of conditions for reading data from other tables into the enclosing query. The rules for subqueries vary according to purpose. The data they retrieve is always read-only.
Union queries provide the ability to extract rows with matching formats from different sets into a unified set that applications can use as if it were a single, read-only table. The subsets retrieved from the tables do not need to be related to one another—they simply have to match one another structurally.
Firebird Related Interview Questions
|RDBMS Interview Questions||MySQL Interview Questions|
|Linux Interview Questions||Mac OS X Deployment Interview Questions|
|Windows Administration Interview Questions||Windows Server 2003 Interview Questions|
|SQL Interview Questions||NoSQL Interview Questions|
|Advanced C++ Interview Questions|
Introduction To Client/server Architecture
About Firebird Data Types
Date And Time Types
Blobs And Arrays
From Drawing Board To Database
Creating And Maintaining A Database
Firebird’s Sql Language
Expressions And Predicates
Querying Multiple Tables
Ordered And Aggregated Sets
Overview Of Firebird Transactions In
Programming With Transactions
Introduction To Firebird Programming
Developing Psql Modules
Error Handling And Events
Security In The Operating Environment
Configuration And Special Features
Interactive Sql Utility (isql)
Database Backup And Restore (gbak)
Housekeeping Tool (gfix)
Understanding The Lock Manager
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.