Just a minor question.

As some people experience problems with the size of the node_relationships table with certain setups involving views (and these problems can be severe, when a huge table is being altered a lot), and as that table is mainly related to views, it would make sense not to populate this table when flusing views option is not selected.

This check is done while flushing via boost_cache_get_node_relationships(), with a check 


if (BOOST_FLUSH_VIEWS && module_exists('views')) {
    $router_item = _boost_get_menu_router();
    $relationship = array();
    $relationship[] = array('page_callback' => 'node', 'page_type' => $node->type, 'page_id' => $node->nid);
    $relationships = boost_cache_get_node_relationships($relationship);

but is not done the other way arround, when creating the table with boost_cache_set_node_relationships(). If BOOST_FLUSH VIEWS is not set this will pose a potential performance problem -along with complex innecesary calculations- that could have the only advantage of allowing the activation of views flushing "on the fly". If that "on thefly" activation would b a feature, then an option to disable it would be needed