I have been using toolset for a while but without relationship. I am about to build the attach schema of a "DB" within Toolset, this for the management of events, especially to build sponsor list and session programme for the events. Before I do so I just wanted your expert opinion if this is possible within Toolset/WP or not. Am I pushing the envelop too far.
Example each presentation on the programme will be build with data from 5 different joined tables (CPT) :
Session ID, Presentation ID, Time, Abstract Title, Abstract, Speaker Name, Biography, Photo, Company Name, Country
Most of your online documentation talks about parent/child, some grandparent/parent/child. Just not sure if toolset can be treated as "relational DB" with X joined tables.
Just don't want to start on the project and then it a snag only to find out it is not doable.
Thanks for your feedback.
Phil
Toolset does use a relational database because our Types relationships are split amongst multiple tables using joins.
From your screenshot this is beyond the possibility of our Toolset plugins and would require some highly custom code to achieve what you are trying to achieve.
Unless you take the route of using Post relationships to relate your items, which is definitely possible. I would recommend exploring the option of using the Relationships in Types to achieve your goal.
So essentially each of your tables will be created as Post Types and you can relate them through Types.
Otherwise from this then it would be out of the scope of what toolset can do.
Hi Shane,
Thanks for your quick reply and maybe my question wasn't clear enough. But yes my intention is to use Post Types (like you said each of my tables become a Post Type) and use the relationship that Types provide. My question was more about the intricacy of building multiple relationship between the different tables (Post Types) and build a View including the data from more than 2 tables (Post Types) as per my schema. Ie. be able to pull the company's name for a programme sessions which is in a Post Types 2 to 3 join further and the speaker which is in another Post Types. I hope this make sense?
Also I see that Toolset has a Many-to-Many type of relationship which in a standard DB world is build through 2 x One-to-Many relationships and a bridging/joining table. By using this type of Relationship I might be able to simplify my schema.
Thanks,
Phil
"build a View including the data from more than 2 tables (Post Types) as per my schema. Ie. be able to pull the company's name for a programme sessions which is in a Post Types 2 to 3 join further and the speaker which is in another Post Types. I hope this make sense?"
Ok so this is possible but you will need to combine and nest multiple views in order to achieve this.
Lets say you have a Company, but you want to display the speakers attached to that company.
If you create a template for the company then you can add a view that is listing out Speakers to that template for the company. However this view must have a query filter for relationships added to it. This relationship is then set to the relationship that was created in Types.
So when you go to a Company page on the frontend you can see the Speakers attached to that company.
