树结构查询中逻辑OR的完全外连接的替代方法

时间:2012-10-21 21:23:49

标签: sql postgresql tree hierarchy

我希望标题足够清晰。我一直在为使用简单节点和父子关联表保存在数据库中的树结构实现逻辑AND / OR。 示例树具有如下结构:

nodes and their children

示例树结构查询如下:

A contains children of certain types, which in turn contain other nodes

查询模式中的双线表示A有一个类型为B的子节点(在其子节点下面的某个地方)或者C.我已经实现了A - > HASCHILD - > C - > HASCHILD - > E具有内连接,并且A - >; HASCHILD - > B - > HASCHILD - > E是这样实现的。 诀窍是在A上连接这两个分支。由于这是一个OR操作,B分支或C分支可能不存在。我能想到的唯一方法是使用A的node_id作为键来使用两个分支的完整外连接。为了避免细节,让我从我的SQL查询中提供这个简化的片段:

    WITH A as (....),
    B as (....),
    C as (....),
    ......

SELECT * 
      from
          A
          INNER JOIN A_CONTAINS_B ON  A.NODE_ID = A_CONTAINS_B.parent
          INNER JOIN B ON A_CONTAINS_B.children @> ARRAY[B.NODE_ID]
          INNER JOIN .....

          full OUTER JOIN -- THIS IS WHERE TWO As ARE JOINED
          (select
          A2.NODE_ID AS A2_NODE_ID
          from
          A2
          INNER JOIN A_CONTAINS_C ON A2.NODE_ID = C_CONTAINS_C.parent
          INNER JOIN C ON A_CONTAINS_C.children @> ARRAY[C.NODE_ID]
          INNER JOIN ....) 
          as other_branch
          ON other_branch.A2_NODE_ID = A.NODE_ID

此查询链接两个使用node_id实际表示相同A的As,如果B或C不存在,则不会中断。 结果集当然有重复,但我可以忍受。但是我不能想到在这种情况下实现OR的另一种方法。 AND很简单,它们是内连接,但左外连接是让我连接As的唯一方法。两个分支的虚拟列的UNION ALL不是一个选项,因为在这种情况下我无法连接As。

你对我在这里做的事情有其他选择吗?

更新

TokenMacGuy的建议给了我一条比我现在更清晰的路线。我应该记得UNION。 使用他建议的第一种方法,我可以应用查询模式分解,这将是使用逻辑运算符分解查询的一致方法。以下是我将要做的事情的直观表示,以防万一它可以帮助其他人可视化过程:

Tree query decomposition

这有助于我做很多好事,包括创建一个好的结果集,其中查询模式组件链接到结果。 我故意避免使用表或其他上下文的细节,因为我的问题是如何加入查询结果。我如何处理数据库中的层次结构是一个我想避免的不同主题。我会在评论中添加更多细节。这基本上是由层次表伴随的EAV表。为了防止有人想看到它,在遵循TokenMacGuy的建议之后,这是我正在运行的查询,没有任何简化:

WITH
    COMPOSITION1 as (select comp1.* from temp_eav_table_global as comp1
                      WHERE
                      comp1.actualrmtypename = 'COMPOSITION'),
    composition_contains_observation as (select * from parent_child_arr_based),
    OBSERVATION as (select obs.* from temp_eav_table_global as obs
                        WHERE
                        obs.actualrmtypename = 'OBSERVATION'),
    observation_cnt_element as (select * from parent_child_arr_based),
    OBS_ELM as (select obs_elm.* from temp_eav_table_global as obs_elm
                        WHERE
                        obs_elm.actualrmtypename= 'ELEMENT'),

     COMPOSITION2 as (select comp_node_tbl2.* from temp_eav_table_global as comp_node_tbl2
                          where
                          comp_node_tbl2.actualrmtypename = 'COMPOSITION'),
    composition_contains_evaluation as (select * from parent_child_arr_based),
    EVALUATION as (select eva_node_tbl.* from temp_eav_table_global as eva_node_tbl
                            where
                            eva_node_tbl.actualrmtypename = 'EVALUATION'),
    eval_contains_element as (select * from parent_child_arr_based),
    ELEMENT as (select el_node_tbl.* from temp_eav_table_global as el_node_tbl
                            where
                            el_node_tbl.actualrmtypename = 'ELEMENT')



select
                      'branch1' as branchid,
                      COMPOSITION1.featuremappingid as comprootid,
                      OBSERVATION.featuremappingid as obs_ftid,
                      OBSERVATION.actualrmtypename as obs_tn,
                      null as ev_ftid,
                      null as ev_tn,
                      OBS_ELM.featuremappingid as obs_elm_fid,
                      OBS_ELm.actualrmtypename as obs_elm_tn,
                      null as ev_el_ftid,
                      null as ev_el_tn

                      from
                      COMPOSITION1
                      INNER JOIN composition_contains_observation ON COMPOSITION1.featuremappingid = composition_contains_observation.parent
                      INNER JOIN OBSERVATION ON composition_contains_observation.children @> ARRAY[OBSERVATION.featuremappingid]
                      INNER JOIN observation_cnt_element on observation_cnt_element.parent = OBSERVATION.featuremappingid
                      INNER JOIN OBS_ELM ON observation_cnt_element.children @> ARRAY[obs_elm.featuremappingid]

UNION

SELECT                  
                        'branch2' as branchid,
                        COMPOSITION2.featuremappingid as comprootid,
                        null as obs_ftid,
                        null as obs_tn,
                        EVALUATION.featuremappingid as ev_ftid,
                        EVALUATION.actualrmtypename as ev_tn,
                        null as obs_elm_fid,
                        null as obs_elm_tn,
                        ELEMENT.featuremappingid as ev_el_ftid,
                        ELEMENT.actualrmtypename as ev_el_tn                       
                  from
                      COMPOSITION2
                      INNER JOIN composition_contains_evaluation ON  COMPOSITION2.featuremappingid = composition_contains_evaluation.parent
                      INNER JOIN EVALUATION ON composition_contains_evaluation.children @> ARRAY[EVALUATION.featuremappingid]
                      INNER JOIN eval_contains_element ON EVALUATION.featuremappingid = eval_contains_element.parent
                      INNER JOIN ELEMENT on eval_contains_element.children @> ARRAY[ELEMENT.featuremappingid]

1 个答案:

答案 0 :(得分:3)

与∨相关的关系是⋃。您可以使用uniona JOIN b JOIN ea JOIN c JOIN e结合使用,或者只使用b和c的联合并加入最终的组合关系,例如a JOIN (b UNION c) JOIN e

更完整:

SELECT *
FROM a
JOIN (
    SELECT
        'B' source_relation,
        parent,
        b.child,
        b_thing row_from_b,
        NULL row_from_c
    FROM a_contains_b JOIN b ON a_contains_b.child = b.node_id

    UNION
    SELECT
        'C',
        parent
        c.child,
        NULL,
        c_thing
    FROM a_contains_c JOIN c ON a_contains_c.child = c.node_id
) a_c ON A.NODE_ID = a_e.parent
JOIN e ON a_c.child = e.node_id;