在与摔跤超过一个星期后,我认为我最终有一个工作功能.这并没有针对性能进行优化(哦,循环！),但在我可以处理性能的同时暂时完成工作.生成的OrientDB服务器端函数(用javascript编写)：

功能：

// Clear prevIoUs runs
db.command("truncate class tmp_Then");
db.command("truncate class tmp_Events");

// Get all distinct events
var distinctEvents = db.query("select from Events group by event");

// Send 404 if null,otherwise proceed
if (distinctEvents == null) {
  response.send(404,"Events not found","text/plain","Error: events not found" );
} else {
  var edges = [];

  // Loop through all distinct events
  distinctEvents.forEach(function(distinctEvent) {
    var newEvent = [];
    var rid = distinctEvent.field("@rid");
    var eventType = distinctEvent.field("event");

    // The main query that finds all *direct* descendents of the distinct event
    var result = db.query("select from (traverse * from (select from Events where event = ?) where $depth <= 2) where @class = 'Events' and $depth > 1 and @rid in (select from Events group by event)",[eventType]);

    // Save the distinct event in a temp table to create temp edges
    db.command("create vertex tmp_Events set rid = ?,event = ?",[rid,event]);
      edges.push(result);
    });

  // The edges array defines which edges should exist for a given event
  edges.forEach(function(edge,index) {
    edge.forEach(function(e) {
      // Create the temp edge that corresponds to its distinct event
      db.command("create edge tmp_Then from (select from tmp_Events where rid = " + distinctEvents[index].field("@rid") + ") to (select from tmp_Events where rid = " + e.field("@rid") + ")");
    });
  });

  var result = db.query("select from tmp_Events");
  return result;
}

小贴士：

>临时表似乎是必要的.我试图在没有临时表(类)的情况下这样做,但我不确定它是否可以完成.我需要模拟原始数据中不存在的边缘.> Traverse在编写主查询时非常有帮助.遍历一个事件,找到其直接,独特的后代是相当简单的.>具有在Javascript中编写存储过程的能力令人敬畏.这本来是sql中的噩梦.> omfg循环.我计划优化它并继续使它更好,所以希望其他人可以找到它的一些用途.