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

  • Home
  • SEARCH
  • 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 777703
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T19:38:58+00:00 2026-05-14T19:38:58+00:00

Say I have a post table containing the fields post_id and parent_post_id . I

  • 0

Say I have a post table containing the fields post_id and parent_post_id. I want to return every record in the post table with a count of the “depth” of the post. By depth, I mean, how many parent and ancestor records exist.

Take this data for example…

post_id   parent_post_id
-------   --------------
1         null
2         1
3         1
4         2
5         4

The data represents this hierarchy…

1
|_ 2
|  |_ 4
|     |_ 5
|_ 3

The result of the query should be…

post_id   depth
-------   -----
1         0
2         1
3         1
4         2
5         3

Thanks in advance!

  • 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-05-14T19:38:59+00:00Added an answer on May 14, 2026 at 7:38 pm

    If you’re making a lot of queries like this, you may find that a nested set model is more appropriate than the adjacency list you’re asking about. There’s a good discussion of both models here.

    In any event, to do what you’re asking with an adjacency list you’re looking at either recursion in the application layer, or storing the level as a 3rd column.

    ETA: if your level count isn’t terribly high, you can do it with self joins:

    e.g. nodes with 2 ancestors:

    SELECT t1.node 
    FROM mytable AS t1
    JOIN mytable AS t2 ON t1.parent = t2.node
    JOIN mytable AS t3 ON t2.parent = t3.node
    WHERE t3.parent IS NULL;
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

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.