Closed joebudi closed 2 years ago
What's the budibase way work around till this is implemented?
lets say I've a TASK table and want to have SUB-TASKS. Could be 2 levels or may be 3 levels
for example: Main Task -----> Level 1 ->Sub Task 1 -----> Level 2 -> SubSub Task 1 -----> Level 3 -> SubSub Task 2
Hey @hshifaz Do you have an illustration of how this would work? This may be helpful to visualise what you mean.
Hey @hshifaz Do you have an illustration of how this would work? This may be helpful to visualise what you mean.
@joebudi If we are to visualize in terms of table relationships, the following two examples should be good enough.
Main Task -----> id = 1 order = 0
->Sub Task 1 ----->id = 2 parent_id = 1 order = 0
-> SubSub Task 1 -----> id = 3 parent_id = 2 order = 0
-> SubSub Task 2 -----> id = 4 parent_id = 2 order = 1
Main Task -----> id = 5 order = 1
database
id_name___parent_id__order 1Main Task ____null or 0_0 2_Sub Task 11___0 3___SubSub Task 12___0 4___SubSub Task 22_____1 5Main Task 1__null or 0 ____1
use like nestable menu Nestable
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bump
Hi, is this still under consideration? Would really be helpful for creating things like role hierarchy (manager / subordinates), etc
Bump. Necessary for implementing BOMs.
Bump
Is there any update on this?
Bump
Relationships should allow you to pick the table you are building the relationship in. This will allow for parent/child records in the same table.
Originally posted by @lylebrown in https://github.com/Budibase/budibase/discussions/1034