[
https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688619#action_12688619
]
Ashish Vijaywargiya commented on OFBIZ-2205:
--------------------------------------------
Hello Abhinav,
Please take a look at the ongoing discussion on creating View entity using
another View entity.
Here is the link to see the discussion.
http://www.nabble.com/One-view-entity-member-of-another-view-entity-to22657407.html
Specially notice the David's reply in that thread. (For your reference pasting
the contents here)
------------
Is it feasible? That depends on the constraints you're working with.
It does usually work and can be done, but also often results in asking
the database to do more than your code really needs it to do (ie
including things in the joins that you don't need, significantly
slowing performance). The same is true of poorly defined view-entities
with normal (non-view) member entities, but there is more of a
tendency for that with views of views.
-David
----------------------
So now we can say that we should avoid the use of View that uses another View
entity for data preparation.
We should find the alternate approach for doing the same thing instead of using
ApproverAndCandidate, InterviweeAndInterviewer, PersonAndEmployeeAction view
entities to solve our purpose.
--
Ashish Vijaywargiya
> Implemented recruitment in HR module
> ------------------------------------
>
> Key: OFBIZ-2205
> URL: https://issues.apache.org/jira/browse/OFBIZ-2205
> Project: OFBiz
> Issue Type: New Feature
> Components: humanres
> Affects Versions: SVN trunk
> Environment: Windows XP Professional (5.1, Build 2600) Service Pack
> 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0,
> apache-ant-1.7.0
> Reporter: Abhinav Vaid
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: HR_Recruitment.patch, HR_Recruitment.patch,
> HR_Recruitment.patch, HR_Recruitment.patch
>
>
> In this patch we have included recruitment in the HR module.
> Recruitment performs tasks such as admin can create new job requisitions.
> He can update or delete new job requisitions.
> Now once the job requisition has been added, it is visible to all the
> employees.
> Then if interested employee wants to apply for the job requisition he sends
> it for approval to his superior.
> Superior from his login can check who all have applied for job requisition.
> He can update the status and same is reflected at employee's end.
> Here admin can also create new interview types and he can store the
> information of the diffrent interviews of employees.
> We have created Security groups:
> HUMANRES_APPROVER
> HUMANRES_EMPLOYEE
> We have created Security permissions:
> HUMANRES_APPROVE
> We have created Login Id's :
> demoadmin belongs to FULLADMIN security group
> demoapprover belongs to HUMANRES_APPROVER security group
> demoemployee belongs to HUMANRES_EMPLOYEE security group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
