Scribd Logo
Încărcați

Bine ați venit la Scribd!

  • (Development Simply Put) How To Apply Recursive SQL Selections On Hierarchical Data

    Încărcat de

    Ahmed Tarek Hasan
    29 vizualizări9 pagini
    http://developmentsimplyput.blogspot.com/2013/05/how-to-apply-recursive-sql-selections.html Sometimes we work on systems where a hierarchical data structure exists on some entities like employees and their managers. Both employees and managers can be called employees but there is a self join relation between them as each employee must have a manager. We all faced the situation when we need to get the info about each employee and his/her direct manager. At this point we used to join between the employees (child) table and itself (parent) on the condition that the parent id of the child is equal to the id of the parent. This is good. But, what about if we need to get the hierarchical tree of managers of a certain employee not just his direct manager. It seems as we just need to the same join but more than one time till we are up all the way to the head manager. This is somehow logical but how can we do this number of joins and we don't know the number of levels up to the head manager?!!! If you want to know more, you can read this article.

    Titlu original

    [Development Simply Put] How to Apply Recursive SQL Selections on Hierarchical Data

    Drepturi de autor

    © Attribution Non-Commercial (BY-NC)

    Formate disponibile

    PPTX, PDF, TXT sau citiți online pe Scribd

    Vi se pare util acest document?

    Este necorespunzător acest conținut?

    Raportați acest document
    http://developmentsimplyput.blogspot.com/2013/05/how-to-apply-recursive-sql-selections.html Sometimes we work on systems where a hierarchical data structure exists on some entities like employees and their managers. Both employees and managers can be called employees but there is a self join relation between them as each employee must have a manager. We all faced the situation when we need to get the info about each employee and his/her direct manager. At this point we used to join between the employees (child) table and itself (parent) on the condition that the parent id of the child is equal to the id of the parent. This is good. But, what about if we need to get the hierarchical tree of managers of a certain employee not just his direct manager. It seems as we just need to the same join but more than one time till we are up all the way to the head manager. This is somehow logical but how can we do this number of joins and we don't know the number of levels up to the head manager?!!! If you want to know more, you can read this article.

    Drepturi de autor:

    Attribution Non-Commercial (BY-NC)
    Descărcați ca PPTX, PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    29 vizualizări9 pagini

    (Development Simply Put) How To Apply Recursive SQL Selections On Hierarchical Data

    Încărcat de

    Ahmed Tarek Hasan
    http://developmentsimplyput.blogspot.com/2013/05/how-to-apply-recursive-sql-selections.html Sometimes we work on systems where a hierarchical data structure exists on some entities like employees and their managers. Both employees and managers can be called employees but there is a self join relation between them as each employee must have a manager. We all faced the situation when we need to get the info about each employee and his/her direct manager. At this point we used to join between the employees (child) table and itself (parent) on the condition that the parent id of the child is equal to the id of the parent. This is good. But, what about if we need to get the hierarchical tree of managers of a certain employee not just his direct manager. It seems as we just need to the same join but more than one time till we are up all the way to the head manager. This is somehow logical but how can we do this number of joins and we don't know the number of levels up to the head manager?!!! If you want to know more, you can read this article.

    Drepturi de autor:

    Attribution Non-Commercial (BY-NC)
    Descărcați ca PPTX, PDF, TXT sau citiți online pe Scribd
    Indicator pentru conținut neadecvat
    din 9

    Intentionally left empty

    Intentionally left empty

    Sometimes we work on systems where a hierarchical data structure exists on some entities like employees and their managers. Both employees and managers can be called employees but there is a self join relation between them as each employee must have a manager. We all faced the situation when we need to get the info about each employee and his/her direct manager. At this point we used to join between the employees (child) table and itself (parent) on the condition that the parent id of the child is equal to the id of the parent. This is good. But, what about if we need to get the hierarchical tree of managers of a certain employee not just his direct manager. It seems as we just need to the same join but more than one time till we are up all the way to the head manager. This is somehow logical but how can we do this number of joins and we don't know the number of levels up to the head manager?!!! If you want to know more, you can read this article. "If you can't explain it simply, you don't
    understand it well enough" -Albert Einstein

    [Development Simply Put] How To Apply Recursive SQL Selections On Hierarchical Data

    Wh I am "Ahmed Tarek" the owner and y? author of the "Development Simply Put" blog.
    During my career days and day after day I got more confident that it's all about sharing not the title you have. I believe that everyone has something to share whatever small he thinks of it. Sometimes a great idea comes out of just a tiny idea and the same for knowledge. I always try to gain knowledge and learn new skills and I found that the best way to learn is to try to teach what you already know. This makes you think of the best simplest way to explain complex logic which makes you spot some points may be even yourself didn't recognize in the first time. The greatest thing in the human mind is that it carries out too complicated operations and finally presents it into a simple form, so why do we always try to re-complicate things? This is what encouraged me to start my blog -Development Simply Put (http://developmentsimplyput.blogspot.com)- trying to do my best to simplify main concepts in IT development and share my humble knowledge in this field. "If you can't explain it simply, you don't
    understand it well enough" -Albert Einstein

    Link s
    Blog Link: http://developmentsimplyput.blogspot.com Facebook Page: https://www.facebook.com/DevelopmentSimplyPut Google+ Page: https://plus.google.com/115238148611061640682 LinkedIn Group: http://www.linkedin.com/groups/Development-Simply-Put-5024295 RSS 2.0 Feed: http://developmentsimplyput.blogspot.com/feeds/posts/default?alt=rss Atom 1.0 Feed: http://developmentsimplyput.blogspot.com/feeds/posts/default Android RSS App: http://www.appsgeyser.com/336849 Follow Link: http://www.blogger.com/follow-blog.g?blogID=852966703260024356 Random Post: http://developmentsimplyput.blogspot.com/?random
    "If you can't explain it simply, you don't understand it well enough" -Albert Einstein

    Want To Offer Help?(liked, hated, good, bad, missing, ......) 1. Comment & provide feedback
    2. Answer the blog survey ( http://www.quibblo.com/quiz/idVKX2u/Development-Simply-Put-Blog-Survey ) 3. Follow ( http://www.blogger.com/follow-blog.g?blogID=852966703260024356) 4. Subscribe ( http://developmentsimplyput.blogspot.com/feeds/posts/default?alt=rss) 5. Share blog links
    "If you can't explain it simply, you don't 6. Invite friends whom you think will be understand it well enough" -Albert Einstein

    interested

    My Resume: LinkedIn: http://www.linkedin.com/in/atarekhasan Yatedo: http://www.yatedo.com/atarekhasan Zerply: http://zerply.com/ahmed-tarek-hasan/public Stackoverflow: http:// stackoverflow.com/users/1284593/ahmed-tarek-hasan My Social Accounts: Facebook: https://www.facebook.com/ahmed.t.hasan Google+: https://plus.google.com/u/0/117461717174836938716 Twitter: https://twitter.com/AhmedTarekHasa1 StumbleUpon: http ://www.stumbleupon.com/stumbler/AhmedTarekHasan/likes Pinterest: http://pinterest.com/ahmedtarekhasan
    "If you can't explain it simply, you don't understand it well enough" -Albert Einstein

    About Me

    S-ar putea să vă placă și