Meta Box Relationships uses a dedicated mb_relationships table (with from, to, and type columns) to model links between any two WordPress objects. A book-to-author link, a project-to-team-member link, an article-to-related-tag link all live in the same table, distinguished by the type column. That design keeps relationships fast and queryable, but the default WordPress admin shows none of the relationship data on the post list, so editors open each record just to see what is linked.

SleekView reads the mb_relationships table and joins the related side into the column set automatically. A books table can show 'Authors' as a column with related author names rendered inline; an author table can show 'Books' as a count or as a list. Filter by relationship type to find records with no links, records with more than N links, or records linked to a specific other record. Inline edits add or remove relationship rows through Meta Box's own API so cache invalidation and registered hooks still apply.

The same mechanism covers user-to-post, term-to-post, and arbitrary cross-type relationships. Saved views per role mean editors only see the relationships they own, and exports to CSV produce flat join rows ready for spreadsheets or external systems. The relationship table stays authoritative; the admin just finally renders the joined data.

Meta Box Relationships made a clean architectural choice: store links between WordPress objects in a dedicated mb_relationships table with from, to, and type columns rather than smuggling them through serialized postmeta. That design pays off in queryability. Joining books to authors, projects to team members, or articles to related tags is a single indexed query instead of an N-way scan of wp_postmeta.

The cost has always been the admin layer. WordPress's list table machinery does not know about mb_relationships, so the related side stays invisible unless someone writes a custom column. Editors open each record to see what is linked, developers build one-off admin pages for relationship-heavy content models, and orphan records hide in plain sight.

SleekView reads the relationship table the way it was designed to be read. The related side renders inline as a column, filters cover orphan detection and link counts, and inline edits route through Meta Box's API so existing hooks continue to fire. The join rows stay where Meta Box put them, and the admin finally surfaces the relationships those rows were designed to represent.