You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a documents table that keeps metadata on externally saved documents and also tracks newer versions of documents, i.e. replacing older documents that were previously referred to in a row.
Looks like this:
So whenever a document replaces an existing one, the replaced document is referenced in the column "rel_replaces_id". The same goes for related documents ("referenced") and documents that are newer versions of themselves ("amended").
Since one can't create a 1-n relationship to the same table w/i Budibase, what's the alternative beside keeping this information in join tables via a many-to-many rel?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've got a documents table that keeps metadata on externally saved documents and also tracks newer versions of documents, i.e. replacing older documents that were previously referred to in a row.
Looks like this:
So whenever a document replaces an existing one, the replaced document is referenced in the column "rel_replaces_id". The same goes for related documents ("referenced") and documents that are newer versions of themselves ("amended").
Since one can't create a 1-n relationship to the same table w/i Budibase, what's the alternative beside keeping this information in join tables via a many-to-many rel?
Thanks for any input / ideas!
Beta Was this translation helpful? Give feedback.
All reactions