One-to-One relationship

[SkrOYC]

This has been talked a lot of times so I'll try to go straight to the point

One-table-multiple-slices vs multiple tables with auto creating children via actions on parent row save.

---

Currently I use the one-table-multiple-slices approach when it comes to 1-to-1

The thing is that the "child" record (it's weird to call it like that since it's the same row currently) needs to be added at the same time that the parent, and same applies to a grandchild because I have two 1-to-1 on the same table, 3 slices basically. So the one-table-multiple-slices sound like the right way for this case.

My problem with this current scenario is that actions are attached to the table, not the slice, so I have a looooot of actions on the same table and also managing views is quite tedious.

---

My problem:
I'm thinking of the usage of this one-table-multiple-slices outside of AppSheet. How does it works on other systems? How standard is this thing? Would you advice this or the second way?

Also, what's your take on managing actions when there are many slices?

Thanks!

@MultiTech @1minManager @Suvrutt_Gurjar @Marc_Dillon @Aurelien @Joseph_Seddik @Steve @Grant_Stead @WillowMobileSys (no particular order)