Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8128835
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T08:03:41+00:00 2026-06-06T08:03:41+00:00

Is the following entity relation correct? I am trying to link employee, timesheet and

  • 0

Is the following entity relation correct? I am trying to link employee, timesheet and approver table.

There are few other tables and fields but for this question my main concern is following three tables. One employee can have more than timesheet approver.

Employee
--------
EmpID pk
Name
TimeSheet
------------
TSHEET_ID PK
FK_EmpID FK
Approved_By
Timesheet_Approver (one employee can have more than one approver
                    but only one will be approving the timesheet)
------------------
EmpID
Approver_EmpID 

Employee Table Data:

EmpID Name
----- -----
1     john
2     david
3     mark

Timesheet Approver Data:

EmpID Approver
----- --------
1     2
1     3
2     3

Timesheet

TSID EMPID APPROVED_BY
---- ----- -----------
101  1     2
102  1     3
103  2     3

OR this looks okay?

enter image description here

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T08:03:43+00:00Added an answer on June 6, 2026 at 8:03 am

    My Suggestion

    Why do you want Approver as a seperate table? Can you keep a Bit Field like IsApprover in Employee table? Otherwise you are creating redundancy

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the following entity with the following relation: @Entity @Table(name = bpr_user) public
I have the following 2 entities: @Entity(name = Employee) @Table(name = EMPLOYEE) public class
I have the following @OneToOne relation: @Entity @Table(name=USER) public class User implements Serializable{ private
I have the following two entities: @Entity class Relation{ @ManyToOne private User user; //some
I have the following entity class : @Entity @Table(name = THE_TREE, catalog = ,
I have an entity mapped as following: @Entity @Table(name = Groups) @IdClass(value = GroupId.class)
Consider the following code: @Entity @Table(name = a) public class A implements Serializable {
I have the following relation of three classes: @Entity public class User{ @OnetoMany List<Attribute>
I have written the following code: @Entity @Table(name=person) @Inheritance(strategy=InheritanceType.JOINED) public class Person { private
For each entity that has a one to many relation with other entity when

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.