Based on Traversing tree-like data in a relational database using SQL question, I would like to know how the way regularly used to describe tree-like data on relational databases considering physical implications?
I'm assuming that the RDBMS has not special features to handling that other than regular SQL ANSI or common available features.
In doubt I'm always interested on MySQL and PostgreSQL and eventually SQLite.