relational form doesn't allow us to perform graph operations such as
shortest path quite efficiently. I'm wondering if storing the graph as
objects would be better? How should I design the schema? Thanks!
Two books:
Inside Microsoft SQL Server 2005: T-SQL Querying by Itzik Ben-Gan
and
Trees and Hierarchies in SQL for Smarties by Joe Celko
have useful information on representing graphs in databases including DDL and DML.
|||Are you basically talking about the classic "traveling salesman" problem?sql