Many thanks for the link.
The underlying database table has the following columns -
ID, Name, Type, Parent Name, Parent Type.....with primary key on ID.
I tried creating a VO from this table and a View link mapping Name & Parent Name.
Using this structure, I created a hierarchy viewer on the page.
However, during runtime, all the nodes were show individually instead as a hierarchy.
Based on this scenario, I have some queries to ask -
1) Is it mandatory to have "Name" column as primary key , with Parent Name as a self referencing foreign key mapping back to Name.
2) If "Name" cannot be makred as a Primary key, can the hierarchy viewer model can still be achieved using view link or should i opt the programmatic way to create each node.
Using the below hierarchical query, can I achieve hierarchical model avoid self referencing constraints? -
WITH OBJECTS AS (SELECT name, parent_name
CONNECT BY NOCYCLE PRIOR name, parent_name
START WITH parent_name = : parent_name)
SELECT name, parent_name
The issue has been resolved.