Professional Documents
Culture Documents
DDM Manual 1
JAI SHRIRAM
ENGINEERING COLLEGE
(Approved by AICTE, New Delhi, Affiliated to Anna University, Chennai,
Accredited by NAAC, NBA Accredited for ECE & CSE)
Dharapuram Road, Avinashipalayam, Tirupur – 638 660.
LABORATORY RECORD
Name ……………………………………………………………………..
Branch ……………………………………………………………………..
Course ……………………………………………………………………..
code &
Name
Page
S.No. Date Content Marks Signature
No.
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
AIM
To study about database development life cycle and problem definition and requirement analysis
scope and constraints.
OVERVIEW OF DDM
Waterfall model
This is the most common of all software models [Pressman, 2007]. The phases in
the waterfall cycle are: project planning, requirements definition, design, development,
testing, and installation and acceptance (See Figure 1). Each of these phases receives an
3
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
input and produces an output (that serves as the input for next phase) in the form of
deliverables.
The waterfall model has a documentation driven approach which, from the user’s point
of view, is considered one of its main weaknesses.The system specifications, which are
finalized early in the lifecycle, may be written in a non-familiar style or in a formal language
that may be difficult for the end user to understand [Schach, 2008]. Generally, the end user
agrees to these specifications without having a clear understanding of what the final product
will be like. This leads to misunderstood or missing requirements in the software requirements
specification.
Prototype model: In this life cycle model, the developers create a prototype of the
application based on a limited version of the user requirements [Pfleeger and Atlee, 2010].
The prototype consists mainly of a “hallow graphics” which shows some basic and simple
functionality. However, this may create a problem because the user may view the prototype
as it were the final product overlooking some of the requirements specified in the SRS
which may not be met fully by this “final product” [Pfleeger and Atlee, 2010]
4
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
Spiral model: This model is a combination of the prototyping and waterfall model [Pfleeger
and Atlee, 2010]. Starting with the requirements and a development plan, thesystem
prototypes and the risks involved in their developments are analyzed through aniterative
process. During each iteration alternative prototypes are considered based uponthe
documented constraints and risks of the previous iteration.
As we have shown in the previous paragraphs, each of the traditional lifecycle models
is missing at least one of the four properties required for database system development. In
5
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
this section the authors propose a new lifecycle model that is adapted from the traditional
lifecycle and which is enhanced for database system development.
After the previous phase has been completed it is necessary to analyze the data to
consider issues of extreme importance such as feasibility, cost, scope and boundaries,
performance issues, security issues, portability requirements, maintenance and the design
model of the expected system. This analysis of the requirements and organizational data
helps to identify potential problems and constraints that could arise during development
phases. Once the aforementioned requirements and issues have been thoroughly analyzed
it is necessary to envision a timeline for future work database is implemented using the
physical design documents developed earlier during the design phase. The database
implementation and loading phase includes steps such as the follows: creating database
tables, populating the tables, building constraints and querying the data.
The Database Initial Study:
In the Database initial study, the designer must examine the current system’s
operation within the company and determine how and why the current system fails.
The overall purpose of the database initial study is to:
• Analyze the company situation.
• Define problems and constraints.
• Define objectives.
• Define scope and boundaries.
a. Analyze the Company Situation:
The company situation describes the general conditions in which a company
operates, its organizational structure, and its mission. To analyze the company
situation, the database designer must discover what the company’s operational
components are, how they function, and how they interact.
6
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
7
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
CONCLUSION
A complete and correct database system is difficult to create if the SDLC does not take into
account the intrinsic characteristics of the system to be developed and itself does not accommodate
properties like scope restriction, progressive enhancement, incremental planning and pre-defined
structure. As indicated before, traditional SDL Cs lack at least one of the aforementioned properties
making them not all suitable for the development of DBMSs, particularly, when the demands on the
DBMS are unpredictable. One of main characteristics of this new proposed model is that it makes
emphasis on activities that go back and forth between phases allowing either the incorporation of
new requirements, if needed, or the correction of incomplete or misunderstood requirements. The
idea is to allow for a system that is more flexible of the realities of developing a DBMS.
EX.NO:2 DATABASE DESIGN USING CONCEPTUAL MODELING (ER-EER)
TOP-DOWN APPROACH MAPPING CONCEPTUAL TO RELATIONAL
DATABASE AND VALIDATE USING NORMALIZATION
8
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
AIM
ALOGRITHM
Consider following databases and draw ER diagram and convert entities and
relationship to relation table for a given scenario.
1. COLLEGE DATABASE:
STUDENT (USN, SName, Address, Phone, Gender)
SEMSEC (SSID, Sem, Sec)
CLASS (USN, SSID)
SUBJECT (Subcode, Title, Sem, Credits)
IAMARKS (USN, Subcode, SSID, Test1, Test2, Test3, FinalIA)
2. COMPANY DATABASE:
9
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
RESULT
Thus the Database design using Conceptual modeling and validate using Normalization
was executed successfully
1
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
AIM
ALGORITHM
STEP 1: Start querying after establishing connection in Run SQL Command Line
console window.
STEP 2: After creating table Employee with different fields
STEP 3: Execute various level of constraints in the employee table
STEP 4: If the exceptions is thrown, check the syntax and logics.
STEP 5: If the query is running successfully, stop querying.
QUERIES
TABLE SCHEMA
Output
10
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
UNIQUE CONSTRAINT
CREATE TABLE COMPANY3(ID INT PRIMARY KEY NOT NULL, NAME TEXT NOT
NULL,AGE INT NOT NULL UNIQUE, ADDRESS CHAR(50),SALARY REAL DEFAULT
50000.00);
Output
PRIMARY KEY
Output
10
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
FOREIGN KEY
CREATE TABLE COMPANY6(ID INT PRIMARY KEY NOT NULL, NAME TEXT NOT
NULL, AGE INT NOT NULL, ADDRESS CHAR(50),SALARY REAL);
CREATE TABLE DEPARTMENT1(ID INT PRIMARY KEY NOT NULL, DEPT CHAR(50) NOT
NULL,EMP_ID INT references COMPANY6(ID));
Output
CHECK CONSTRAINT
CREATE TABLE COMPANY5(ID INT PRIMARY KEY NOT NULL, NAME TEXTNOT NULL,
AGE INT NOT NULL, ADDRESS CHAR(50), SALARY REAL CHECK(SALARY > 0));
Output
RESULT
Thus the Creation of a database and writing POSTGRESQL queries for various
constraints was created and executed successfully.
11
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
INTRODUCTION TO VIEWS
A view is an object that gives the user a logical view of data from an
underlying table or tables. We can restrict what users can view by allowing them to see
only a few attributes/columns from a table.
Views may be created for the following:
INSERTING OF VIEW
DELETING VIEW
DROP VIEW
Object Name:
The name of the object for which you are creating the synonym. It can be one of
the following:
Table
View
Sequence
Stored Producer
Function
User Defined Object
Synonym
RESULT
Thus the Creation of a database and writing POSTGRESQL queries for views was
created and executed successfully
12
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
EX.NO:4
Query the database using SQL Manipulation
Aim:
\d CSE;
Output
Output
13
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
\d AI_DS;
Output
Output
\d EEE;
Output
RESULT
Thus the creation of database and writing a SQL queries to retrieve the information
from the table which is stored in the database was executed successfully.
14
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
OVERVIEW OF SQL
The SQL language can be categorized as Data Definition Language (DDL), Data
Manipulation Language (DML), Data Control Language (DCL) and Transactional Control
Language (TCL).
SQL
DDL commands are used to build and modify the structure of the tables and other
objects in the database. When executing a DDL command, it takes effect immediately.
Syntax – CREATE
15
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
Syntax –ALTER
Syntax- RENAME
Syntax – TRUNCATE
Syntax- SELECT
16
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
Syntax-INSERT
Syntax- UPDATE
Syntax- DELETE
17
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
To control transaction Oracle does not made any changes unless we commit. If we
don’t commit the transaction and power goes off or system crashes then the transaction is roll
backed.
COMMIT
Where;
rollback to savepoint-name;
SAVEPOINT
Savepoint savepoint-name;
18
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
AIM
To Implement of Simple Programs in PL/SQL
DESCRIPTION
Basic Syntax
STORED PROCEDURE/FUNCTION
DEFINITION
A procedure or function is a logically grouped set of SQL and PL/SQL
statements that perform a specific task. They are essentially sub-programs. Procedures
and functions are made up of,
• Declarative part
• Executable part
• Optional exception handling part
29
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
OUT: Specifies that the procedure passes a value for this argument back to it’s calling
environment after execution ie. used to return values to a caller of the sub-program.
INOUT: Specifies that a value for the argument must be specified when calling the
procedure and that procedure passes a value for this argument back to it’s calling environment after
execution.
RETURN: It is the datatype of the function’s return value because every function must
return a value, this clause is required.
PROCEDURES
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
commit;
end;$$;
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
DEFINITION
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
CREATE TABLE COMPANY(ID INT PRIMARY KEY NOT NULL, NAME TEXT NOT NULL, AGE
INT NOT NULL, ADDRESS CHAR(50),SALARY REAL);
CREATE TABLE AUDIT( EMP_ID INT NOT NULL, ENTRY_DATE TEXT NOT NULL);
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
RESULT
Thus Stored Procedures/Functions and Constraints and security using Triggers were
implemented successfully.
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
Ex.No:06
Database design using Normalization – bottom-up approach
ER diagram:
Chen Notation
Chen Notation
Representing Relationships
• 1:1 Relationships. The key of one relation is stored in the second relation. Look at
example queries to determine which key is queried most often.
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
• 1:N Relationships.
Parent - Relation on the "1" side.
Child - Relation on the "Many" side.
• Represent each Entity as a relation.
Copy the key of the parent into the child relation.
• CUSTOMER (CustomerID (key), Name, Address, ...)
ORDER (OrderNum (key), OrderDate, SalesPerson, CustomerID (fk))
M:N Relationships. Many to Many relationships can not be directly implemented in
relations.
Solution: Introduce a third Intersection relation and copy keys from
original two relations.
Chen Notation
PROGRAM
CREATE TABLE the_table
( id SERIAL NOT NULL PRIMARY KEY, name varchar, a INTEGER,
b varchar, c varchar);
INSERT INTO the_table(name, a,b,c) VALUES ( 'Chimpanzee' , 1, 'mammals', 'apes'
)
,( 'Urang Utang' , 1, 'mammals', 'apes' ),( 'Homo Sapiens' , 1, 'mammals', 'apes' )
,( 'Mouse' , 2, 'mammals', 'rodents' ),( 'Rat' , 2, 'mammals', 'rodents' )
,( 'Cat' , 3, 'mammals', 'felix' ),( 'Dog' , 3, 'mammals', 'canae' );
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
ALTER TABLE the_table ADD column abc_id INTEGER -- NOT NULL REFERENCES abc_table(id);
UPDATE the_table ani SET abc_id = ins.id FROM ins WHERE ins.a = ani.a AND ins.b
= ani.b AND ins.c = ani.c
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
SELECT a.*, c.a, c.b, c.c FROM the_table a JOIN abc_table c ON c.id = a.abc_id;
RESULT
Thus the ER Database design using E-R model and Normalization was
implemented successfully.
21
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
Ex. No.07
Database Design using IDE /RAD tools(Eg., NetBeans, Visual
Studio)
AIM
To Implement Database Connectivity using ADO in VB
DESCRIPTION:
Procedure for Creating Table
CREATING TABLE-Form2
SELECT * FROM custable1;
CID CNAME CADDR CPHNO CEMAIL
CREATE TABLE stockin (itemno number (4), itemname varchar2 (10), quantity number
(5), price number (5));
Table created.
SELECT * FROM stockin;;
ITEMNO ITEMNAME QUANTITY PRICE
1 SOAP 500 56
1 SOAP 500 56
2 OIL 200 100
3 HAMMAM 100 45
4 SNACKS 50 20
COMMIT;
Commit complete.
30
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
VB SCRIPT:
LOGIN FORM:
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
DELETE:
Private Sub Delete_Click()
Function Calculate()
Text 5.Text=val(Text4.Text) + val (Text3.Text) End Function
OUTPUT
FORM1:
FORM2:
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
FORM3:
RESULT
Thus Database Connectivity using ADO in VB is implemented Successfully.
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
EX.NO:08
Database design using EER-to-ODB mapping
AIM
To implement the database design using EER-to-ODB mapping.
Algorithm
Step 1: For each regular entity type E
• Create a relation R that includes all the simple attributes of E.
• Include all the simple component attributes of composite attributes.
• Choose one of the key attributes of E as primary key for R.
• If the chosen key of E is composite, the set of simple attributes that form it will together
form the primary key of R.
Step 2: For each weak entity type W with owner entity type E
• Create a relation R, and include all simple attributes and simple components of composite
attributes of W as attributes of R.
• In addition, include as foreign key attributes of R the primary key attribute(s) of the
relation(s) that correspond to the owner entity type(s).
Step 3: For each binary 1:1 relationship type R
• Identify the relations S and T that correspond to the entity types participating in R.
Choose one of the relations, say S, and include as foreign key in S the primary key of T.
• It is better to choose an entity type with total participation in R in the role of S.
• Include the simple attributes of the 1:1 relationship type R as attributes of S.
• If both participations are total, we may merge the two entity types and the
relationship into a single relation.
Step 4: For each regular binary 1:Nrelationship type R
• Identify the relation S that represents the participating entity type at the N-
side of the relationship type.
• Include as foreign key in S the primary key of the relations T that represents the
other entity type participating in R.
• Include any simple attributes of the 1:N relationship type as attributes of S.
Step 5: For each binary M:N relationship type R
• Create a new relation S to represent R.
• Include as foreign key attributes in S the primary keys of the relations that represent the
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
participating entity types; their combination will form the primary key of S
• Also, include any simple attributes of the M:N relationship type as attributes of S.
Step 6: For each multi-valued attribute A
• Create a new relation R that includes an attribute corresponding to A plus the primary key
attribute K (as a foreign key in R) of the relation that represents the entity type or
relationship type that has A as an attribute.
• The primary key of R is the combination of A and K. If a multi-valued attribute is
composite, we include its components.
• However, if the participation constraint (min,max) of one of the entity types E
participating in the R has max =1, then the primary key of S can be the single foreign key
attribute that references the relation E’ corresponding to E
• This is because , in this case, each entity e in E will participate in at most one relationship
instance of R and hence can uniquely identify that relationship instance.
Step 7: To convert each super-class/sub- class relationship into a relational schema you
must use one of the four options available.
Let C be the super-class, K its primary key and A1, A2, …, An its remaining attributes and let
S1, S2, …, Sm be the sub-classes.
Option 7A (multiple relation option):
• Create a relation L for C with attributes Attrs(L) = {K, A1, A2, …, An} and PK(L) = K.
• Create a relation Li for each subclass Si, 1 < i < m, with the attributes
ATTRS(Li) = {K} U {attributes of Si} and PK(Li) = K.
• This option works for any constraints: disjoint or overlapping; total or partial.
Option 7B (multiple relation option):
• Create a relation Li for each subclass Si, 1 < i < m, with ATTRS(Li) = {attributes of Si}
U {K, A1, A2, …, An} PK(Li) = K
• This option works well only for disjoint and total constraints.
• If not disjoint, redundant values for inherited attributes.
• If not , entity not total belonging to any sub-class is lost.
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
EMPLOYEE
DEPARTMENT
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
DEPT_LOCATIONS
DNUMBER DLOCATION
PROJECT
WORKS_ON
DEPENDENT
• This option is for specialization whose subclasses are DISJOINT, and T is a type attribute that
indicates the subclass to which each tuple belongs, if any. This option may generate a large
number of null values.
• Not recommended if many specific attributes are defined in subclasses (will result in many
null values!)
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
RESULT
32
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
EX.No:09
Object features of SQL-UDTs and sub-types, Tables using
UDTs, Inheritance, Method definition
AIM
To study about Object features of SQL-UDTs and sub-types, Tables using UDTs, Inheritance,
Method definition
ALGORITHM
The relational model with object database enhancements is sometimes referred to as the object-
relational model. Additional revisions were made to SQL in 2003 and 2006 to add features related to
XML.
The following are some of the object database features that have been included in SQL: Some type
constructors have been added to specify complex objects. These include the row type, which corresponds to
the tuple (or struct) constructor. An array type for specifying collections is also provided. Other collection
type constructors, such as set, list, and bag constructors, were not part of the original SQL/Object
specifications but were later included in the standard.
A mechanism for specifying object identity through the use of reference type is included.
Encapsulation of operations is provided through the mechanism of user-defined types (UDTs) that may
include operations as part of their declaration. These are somewhat similar to the concept of abstract data
types that were developed in programming languages. In addition, the concept of user-defined routines
(UDRs) allows the definition of general methods (operations).
Inheritance mechanisms are provided using the keyword UNDER.
1. User-Defined Types and Complex Structures for Objects
To allow the creation of complex-structured objects, and to separate the declaration of a type from
the creation of a table, SQL now provides user-defined types (UDTs). In addition, four collection types
have been included to allow for multivalued types and attributes in order to specify complex-structured
objects rather than just simple (flat) records. The user will create the UDTs for a particular application as
part of the database schema.
A UDT may be specified in its simplest form using the following syntax:
CREATE TYPE TYPE_NAME AS (<component declarations>);
First, a UDT can be used as either the type for an attribute or as the type for a table. By using a
UDT as the type for an attribute within another UDT, a complex structure for objects (tuples) in
a table can be created, much like that achieved by nesting type construction.
40
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
A mutator function for updating an attribute sets the value of the attribute to a new value. SQL
allows these functions to be blocked from public use; an EXECUTE privilege is needed to have access to
these functions.
In general, a UDT can have a number of user-defined functions associated with it. The syntax
is
INSTANCE METHOD <NAME> (<ARGUMENT_LIST>) RETURNS
<RETURN_TYPE>;
Two types of functions can be defined: internal SQL and external. Internal functions are
written in the extended PSM language of SQL (see Chapter 13). External functions are written in
a host language, with only their signature (interface) appearing in the UDT definition. An external function
definition can be declared as follows:
DECLARE EXTERNAL <FUNCTION_NAME> <SIGNATURE> LANGUAGE
<LANGUAGE_NAME>;
Attributes and functions in UDTs are divided into three categories: PUBLIC (visible at the UDT
interface)
PRIVATE (not visible at the UDT interface) PROTECTED (visible only to subtypes)
It is also possible to define virtual attributes as part of UDTs, which are computed and updated
using functions.
5. Specifying Inheritance and Overloading of Functions
Recall that we already discussed many of the principles of inheritance in Section 11.1.5. SQL has
rules for dealing with type inheritance (specified via the UNDER keyword). In general, both attributes and
instance methods (operations) are inherited. The phrase NOT FINAL must be included in a UDT if subtypes
are allowed to be created under that UDT (see Figure 11.4(a) and (b), where
PERSON_TYPE,STUDENT_TYPE, and EMPLOYEE_TYPE are declared to be NOT FINAL). Associated
with type inheritance are the rules for overloading of function implementations and for resolution of function
names.
These Inheritance rules can be summarized as follows: All attributes are inherited.
The order of supertypes in the UNDER clause determines the inheritance hierarchy.
An instance of a subtype can be used in every context in which a supertype instance is used.
A subtype can redefine any function that is defined in its supertype, with the restriction that the
signature be the same.
When a function is called, the best match is selected based on the types of all arguments.
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
RESULT
Thus Object features of SQL-UDTs and sub-types, Tables using UDTs, Inheritance, Method
definition was successfully executed.
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
AIM
To query the Object-relational database using Objet Query language.
OQL Commands
The tables used for the above program is,
Staffmanagers Table
Staffemployee Table
Staffcontractors Table
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
SELECT Name,Age FROM staffcontractors WHERE Gender <> 'Male' AND Age <> 20;
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)
lOMoARcPSD|29751364
RESULT
The Object-relational databases query using Object Query Language is executed successfully.
43
Downloaded by Bhuvaneshwari M (m.bhuvaneshwari2126@gmail.com)