我正在处理具有层次结构的资产数据库。此外,还有一个“ReferenceAsset”表,它有效地指向资产。参考资产基本上起着重写的作用,但它被选为好像它是一种独特的新资产。其中一个被设置的覆盖是parent_id。SQL Server:查询分层和引用数据
列,其相关的选择层次结构:
资产:ID(主),PARENT_ID
资产参考:ID(主),ASSET_ID(foreignkey->资产),PARENT_ID(总是一个资产)
- --EDITED 5/27 ----
样品培训相关表数据(加入后):
id | asset_id | name | parent_id | milestone | type 3 3 suit null march shape 4 4 suit_banker 3 april texture 5 5 tie null march shape 6 6 tie_red 5 march texture 7 7 tie_diamond 5 june texture -5 6 tie_red 4 march texture
的0(如最后一行)表示被引用的资产。被引用的资产有几个过期的列(在这种情况下,只有parent_id很重要)。
的期望是,如果我从四月中选择所有资产,我应该做的第二选择,以获得匹配查询的全部树枝:
所以最初查询匹配会导致:
4 4 suit_banker 3 april texture
然后CTE后,我们得到了完整的层次,我们的结果应该是这样的(到目前为止,这是工作)
3 3 suit null march shape 4 4 suit_banker 3 april texture -5 6 tie_red 4 march texture
,你会看到,ID的父:-5是存在的,但缺少什么,那是需要的,是被引用的资产,并且引用的资产的母公司:
5 5 tie null march shape 6 6 tie_red 5 march texture
目前我的解决方案适用于此,但它仅限于单一深度的引用(并且我觉得实现非常难看)。
---编辑---- 这是我的主要选择功能。这应该更好地证明真正的复杂性所在:AssetReference。
Select A.id as id, A.id as asset_id, A.name,A.parent_id as parent_id, A.subPath, T.name as typeName, A2.name as parent_name, B.name as batchName,
L.name as locationName,AO.owner_name as ownerName, T.id as typeID,
M.name as milestoneName, A.deleted as bDeleted, 0 as reference, W.phase_name, W.status_name
FROM Asset as A Inner Join Type as T on A.type_id = T.id
Inner Join Batch as B on A.batch_id = B.id
Left Join Location L on A.location_id = L.id
Left Join Asset A2 on A.parent_id = A2.id
Left Join AssetOwner AO on A.owner_id = AO.owner_id
Left Join Milestone M on A.milestone_id = M.milestone_id
Left Join Workflow as W on W.asset_id = A.id
where A.deleted <= @showDeleted
UNION
Select -1*AR.id as id, AR.asset_id as asset_id, A.name, AR.parent_id as parent_id, A.subPath, T.name as typeName, A2.name as parent_name, B.name as batchName,
L.name as locationName,AO.owner_name as ownerName, T.id as typeID,
M.name as milestoneName, A.deleted as bDeleted, 1 as reference, NULL as phase_name, NULL as status_name
FROM Asset as A Inner Join Type as T on A.type_id = T.id
Inner Join Batch as B on A.batch_id = B.id
Left Join Location L on A.location_id = L.id
Left Join Asset A2 on AR.parent_id = A2.id
Left Join AssetOwner AO on A.owner_id = AO.owner_id
Left Join Milestone M on A.milestone_id = M.milestone_id
Inner Join AssetReference AR on AR.asset_id = A.id
where A.deleted <= @showDeleted
我有一个存储过程,需要一个临时表(#temp)并查找层次结构的所有元素。我所采用的策略是这样的:
- 选择整个系统层次结构到一个临时表用逗号分隔的每个整个树枝列表来表示(#treeIDs)
- 获取匹配查询资产整体的层次结构(从#临时)
- 获取所有参考资产所指向的资产从层次结构
- 解析所有参考资产
这适用于现在的层次结构,因为参考的资产永远是拉如果他们不是,我想我会陷入麻烦。我觉得我需要一些更好的递归形式。
这里是我当前的代码,这是工作,但我不感到自豪,我知道这是不稳健(因为它只有在引用底部作品):
第1步。构建整个层次
;WITH Recursive_CTE AS (
SELECT Cast(id as varchar(100)) as Hierarchy, parent_id, id
FROM #assetIDs
Where parent_id is Null
UNION ALL
SELECT
CAST(parent.Hierarchy + ',' + CAST(t.id as varchar(100)) as varchar(100)) as Hierarchy, t.parent_id, t.id
FROM Recursive_CTE parent
INNER JOIN #assetIDs t ON t.parent_id = parent.id
)
Select Distinct h.id, Hierarchy as idList into #treeIDs
FROM (Select Hierarchy, id FROM Recursive_CTE) parent
CROSS APPLY dbo.SplitIDs(Hierarchy) as h
步骤2.选择匹配查询
Select DISTINCT L.id into #RelativeIDs FROM #treeIDs
CROSS APPLY dbo.SplitIDs(idList) as L
WHERE #treeIDs.id in (Select id FROM #temp)
步骤3.所有资产的分支获取所有参考资产在枝头 (参考资产有负的ID值,因此ID < 0部分)
Select asset_id INTO #REFLinks FROM #AllAssets WHERE id in
(Select #AllAssets.asset_id FROM #AllAssets Inner Join #RelativeIDs
on #AllAssets.id = #RelativeIDs.id Where #RelativeIDs.id < 0)
第4步:获取的任何分支在步骤3
Select DISTINCT L.id into #extraRelativeIDs FROM #treeIDs
CROSS APPLY dbo.SplitIDs(idList) as L
WHERE
exists (Select #REFLinks.asset_id FROM #REFLinks WHERE #REFLinks.asset_id = #treeIDs.id)
and Not Exists (select id FROM #RelativeIDs Where id = #treeIDs.id)
我一直在努力,只是显示找到相关的代码。我非常感谢任何能够帮助我找到更好解决方案的人!
你使用的是什么sql版本? http://msdn.microsoft.com/de-de/library/bb677290.aspx – NickD 2013-04-28 07:48:54
sql server 2012,但我们只是切换到它,所以这大部分是写于2008 – haggercody 2013-04-28 07:58:29