many to many db design
My current approach to this is having relationship tables . If I have tables A, B then i have tableAB. I noticed that there is the Xano notion of objects and lists that can be used to achieve similarly. What are the advantages of using the object/list field in a table approach, and any side-effects? 
