As long as the SQL is passed through without modifications (which I assume it does) you'll be able to use CTEs, yes A simple test could be something like this: WITH cte AS ( SELECT * FROM mytable ) SELECT * FROM cte.
As long as the SQL is passed through without modifications (which I assume it does) you'll be able to use CTEs, yes. A simple test could be something like this: WITH cte AS ( SELECT * FROM mytable ) SELECT * FROM cte.
Let's assume the hierachy is mostly read, but isn't completely static. Let's say it's a family tree. Instead, split your nodes and your relationships into two tables.
You can now run arbitary queries that don't involve joining the table back on itself, which would happen if you have the heirachy relationship in the same row as the node. Who has grandparents? Who are uncles?
You avoid all the problems of joining a table to itself via subqueries, a common limitation is 16 subsuqeries. Trouble is, maintaining the ancestor table is kind of hard - best done with a stored procedure.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.