boost_views_pre_render causes issues on lots of nodes

It seems like the simple solution (atleast what I have right now) is in my custom module, I have the following code:

/**
 * Implementation of hook_views_pre_execute().
 * Run before boost and its views portion executesexecutes
 */
function custom_module_views_pre_execute(&$view) {
  if ($view->name == 'photo_gallery_content' && module_exists('boost')) {
    global $_boost_cache_this, $_boost_cache_this_backup;
    $_boost_cache_this_backup = $_boost_cache_this;
    $_boost_cache_this = FALSE;
  }
}

/**
 * Implementation of hook_views_post_render().
 * Run after boost executes
 */
function custom_module_views_post_render(&$view) {
  if ($view->name == 'photo_gallery_content' && module_exists('boost')) {
    global $_boost_relationships, $_boost_cache_this, $_boost_cache_this_backup;
    $_boost_cache_this = $_boost_cache_this_backup;
    if ($_boost_cache_this) {
      $nids = array();
      foreach ($view->result as $item) {
        $nids[] = $item->nid;
      }
      $result = db_query("SELECT nid, type FROM {node} WHERE nid IN (". implode(', ', $nids) .")");
      while($node = db_fetch_object($result)) {
        $GLOBALS['_boost_relationships'][] = array('child_page_callback' => 'node', 'child_page_type' => $node->type, 'child_page_id' => $item->nid);
      }
    }
  }
}

This seems to allow the relationships to exist with a view while keeping the performance relatively fast. I tried this on a page with about 1k nodes in the custom pager and things seem to work just fine (the query takes between 6 and 10 milliseconds). Even separated out on each query, each one should be really fast (though it would add up). What I'm wondering is if there is a way to make what I wrote even most db-agnostic (so it can be queried against mongodb and the like without issues) so that a portion of what I wrote makes its way into boost instead of being in a custom table.

I'm attaching a variant of what I wrote as a patch to the boost module to get this going.

Argh...can't believe I screwed up a simple patch.

Try #2

Hmm, it shouldn't have an effect on things loaded through ajax since nothing it output to the screen. Which patch did you try?

I'm marking off this issue as 'fixed'. It *seems* like this has been resolved in the dev branch of boost. I cannot verify if that works or not but from what I see in the code, node_load operations are no longer occurring which is a good sign :)