Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: Resiliency To New Data Requirements

Re: Resiliency To New Data Requirements

From: Neo <neo55592_at_hotmail.com>
Date: 2 Aug 2006 14:48:15 -0700
Message-ID: <1154555295.338590.101020@s13g2000cwa.googlegroups.com>


After implementing the prior solutions, we find we need to store each department's attributes thus requiring a separate table.

RMDB:
CREATE TABLE dept (deptID, name, ...);

INSERT INTO dept (1, finance);
INSERT INTO dept (2, safety);
INSERT INTO dept (3, personnel);
INSERT INTO dept (4, marketing);

Update employee_dept table, replace field dept with deptID, update data.

Update Query:
SELECT employee.*
FROM (employee INNER JOIN employee_dept ON employee.empID = employee_dept.empID) INNER JOIN dept ON employee_dept.deptID = dept.deptID
WHERE (((dept.name)="safety") AND ((employee.salary)=20000));

DBD:
No change. Original query still ok, returns Mary. (and (select employee instance *)

(select * dept safety)
(select * salary 20000))
Received on Wed Aug 02 2006 - 16:48:15 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US