StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11969440
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-15T12:41:04.693
FavoriteCount
0
LastActivityDate
2012-08-15T12:41:04.693
LastEditDate
LastEditorUserId
0
OwnerUserId
867998
ParentId
11964067
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You need a couple of self-join tables on employee. One represents the supervisor to employee relation. The second represents the peer relationship between employees. Here is the SQL for PostgreSQL drop schema if exists stackoverflow cascade; create schema stackoverflow; set search_path to stackoverflow, public; create table employee ( <pre><code>id serial not null unique, name text not null unique, title text not null, primary key ( id ) </code></pre> ); create table reports ( <pre><code>supervisorid integer not null references employee ( id ) on delete cascade , subordinateid integer not null references employee ( id ) check ( supervisorid != subordinateid ), unique ( supervisorid, subordinateid ), unique( subordinateid ) </code></pre> ); create table peer ( <pre><code>supervisorid integer not null references employee ( id ) on delete cascade , peerid integer not null references employee ( id ) check ( supervisorid != peerid ), unique ( supervisorid, peerid ) </code></pre> ); create or replace view directreports as <pre><code> select supervisor.id as "supervisor id", supervisor.name as "supervisor name", reporting.id as "employee id", reporting.name as "employee name" from employee supervisor, employee reporting , reports where supervisor.id = reports.supervisorid and reporting.id = reports.subordinateid; create or replace view peerreports as </code></pre> select * from directreports, peer, employee <pre><code> where employee.id = peer.peerid and peer.supervisorid = directreports."supervisor id"; </code></pre> insert into employee (name, title) <pre><code>values ( 'c head', 'c head'), ( 'd head', 'd head'), ('c emp1', 'c emp1' ) , ('c emp2', 'c emp2' ) ; insert into reports select employee.id as "supervisorid", reportsto.id as "subordinateid" from employee, employee reportsto where employee.name = 'c head' and reportsto.name in ('c emp1', 'c emp2' ) and reportsto.name != employee.name ; insert into peer select employee.id as "supervisorid", peerto.id as "peer.peerid" from employee, employee peerto where employee.name = 'c head' and peerto.name = 'd head' and employee.id != peerto.id; </code></pre> Here are the typical queries select * from employee; select * from reports; select * from directreports; select * from peer; select * from peerreports, employee where employee.name= 'd head';
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCompany hierarchy data access level implementation in database
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim Child
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.