Delete parent record... ???
Good morning. In a relationship there is table A(parents) and table B (childs) . Since my beginnings in quickbase I have question... ¿Why does quickbase allow you to delete records from table A...
Forum Discussion
Good morning Mr. Shnier.
I think this is a valid question, in my 24 years of experience (software developer) it is the first software I know of that allows you to delete parent records from an entity relationship schema.
About looking for mechanisms to avoid this: I already did it, remove the options to delete all users and with URL - buttons and formulas I can control this situation (show or not a delete button for each record).
Having the capabilities to do what I've just mentioned I don't think will diminish or validate my question.
Thank you
Marcelo Benavides Torres
MarkShnier__You
Qrew Legend
Qrew LegendSorry, I was not trying to say that this would not be a useful feature. I'm just saying that given that this forum is mainly used for a peer to peer help each other type forum, the knowledge of why or why not a feature was build 20 years ago when Quickbase was invented is hard for us to answer.
In my case I block delete for all regular non admin users. Then a provide a checkbox to request deletion and have a Pipeline do the delete if there are no children.
The other reason not to automatically block deleting a parent if there are children, is that there are use cases where the desired outcome is to delete the parent and its children automatically so as not to leave Orphans. This can also be done with a Pipeline
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
In my case I block delete for all regular non admin users. Then a provide a checkbox to request deletion and have a Pipeline do the delete if there are no children.
The other reason not to automatically block deleting a parent if there are children, is that there are use cases where the desired outcome is to delete the parent and its children automatically so as not to leave Orphans. This can also be done with a Pipeline
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- Thanks Mr. Shnier, Just now I understand your comment, this is not the appropriate forum for that question.Thank you!Marcelo Beanvides Torres
- Hi Marcelo,
I think it's an interesting question, though actually in my usage I'm kind of glad that it doesn't work that way. In my database we have a trio of tables: grandparent A, parent B, and child C, which are:
A=Companies
B=Contacts
C=Notes.
We record Notes record that show on both the Contact and the Company record. When a Contact leaves a company, they get deleted because well, too many contacts clutter the search, etc.
However we want to preserve the Notes from our interactions with that person on the Company record because they may be relevant to ongoing business activities. So for us it is a good thing that we can delete that parent record (Contact) without deleting the child (Notes) which still appear on the grandparent (Company) record.
I do understand however that in other situations it can be annoying because you would end up with orphan children. (That does also happen in our system in other areas which I need to do a better job of keeping track of, though it's less common.)
------------------------------
Kim G
------------------------------- HI Kim...It is an interesting example.From the ACADEMIC: the record you are deleting "should" be left in an inactive status, so you never lose a parent's history.I repeat that it is something strictly academic and how the college teach us to take care of information.But the ambiguity of computer science remains: "if it works for you .... that's fine"Thank youMarcelo Benavides
