Fluent NHibernate - 分离表映射

发布于 2024-10-23 00:58:31 字数 2573 浏览 1 评论 0原文

有没有一种方法可以为没有直接引用另一个表的表设置映射?它实际上是从另一个我有直接引用的表中获取它的引用。

这是我到目前为止所拥有的,但我不确定如何在我的元数据模型中映射“LookupValue”。如果 [mdd].DefinitionType 等于 [mdl].LookupType 并且 [md].DataValue 等于 [mdl].LookupKey,则需要映射到 MetaData。

public class MetaData {
    public virtual long TableID { get; set; }
    public virtual MetaDataDefinition Definition { get; set; }
    public virtual int DefinitionID { get; set; }
    public virtual String DataValue { get; set; }
    public virtual MetaDataLookup LookupValue { get; set; }

    public override bool Equals(object obj) { ... }
    public over int GetHashCode() { ... }
}

public class MetaDataDefinition {
    public virtual long ID { get; set; }
    public virtual string DefinitionName { get; set; }
    public virtual string DefinitionType { get; set; }
}

public class MetaDataLookup {
    public virtual string Type { get; set; }
    public virtual string LookupKey { get; set; }
    public virtual string LookupValue { get; set; }

    public override bool Equals(object obj) { ... }
    public over int GetHashCode() { ... }
}

public class MetaDataMap : ClassMap<MetaData> {
    public MetaDataMap() {
        Table("PPOMetaData");
        CompositeId()
            .KeyProperty(x => x.TableID, "TableID")
            .KeyProperty(x => x.DefinitionID, "DefinitionID");

        References(x => x.Defintion, "DefinitionID").Not.LazyLoad().Cascade.All().Fetch.Join();
        Map(x => x.TableID);
        Map(x => x.DataValue);
    }
}
public class MetaDataDefinitionMap : ClassMap<MetaDataDefinition> {
    public MetaDataDefinitionMap() {
        Table("MetaDataDefinitions");
        Id(x => x.ID);
        Map(x => x.DefinitionName);
        Map(x => x.Type);
    }
}

public class MetaDataLookupMap : ClassMap<MetaDataLookup> {
    public MetaDataLookupMap() {
        CompositeId()
            .KeyProperty(x => x.LookupType)
            .KeyProperty(x => x.LookupKey);
        Map(x => x.LookupValue);
    }
}

理想情况下,我希望它运行与此类似的查询:

SELECT     data.TableID, data.DefinitionID, def.DefinitionName, data.DataValue,lu.LookupValue AS DataValue
FROM         dbo.PPOMetadata AS data 
    INNER JOIN dbo.MetaDataDefinitions AS def ON def.ID = data.DefinitionID 
    LEFT OUTER JOIN dbo.MetaDataLookup AS lu ON lu.LookupType = def.Type AND lu.LookupKey = data.DataValue
WHERE data.TableID = 1

就更新能力而言,我唯一要创建、更新或删除的内容将在元数据表中。定义和查找值永远不会改变(至少从应用程序的这一部分来看)。是否可以将“MetaDataLookup”直接映射到元数据模型?如果是这样,有人可以指出我应该关注的正确方向吗?

谢谢!

Is there a way I can setup mapping for a table that doesn't have a direct reference to another table? It actually gets it's reference from another table that I do have a direct reference from.

This is what I have so far, but I'm not sure how to map the "LookupValue" in my MetaData model. It would need to map to MetaData if the [mdd].DefinitionType equals the [mdl].LookupType and the [md].DataValue equals the [mdl].LookupKey.

public class MetaData {
    public virtual long TableID { get; set; }
    public virtual MetaDataDefinition Definition { get; set; }
    public virtual int DefinitionID { get; set; }
    public virtual String DataValue { get; set; }
    public virtual MetaDataLookup LookupValue { get; set; }

    public override bool Equals(object obj) { ... }
    public over int GetHashCode() { ... }
}

public class MetaDataDefinition {
    public virtual long ID { get; set; }
    public virtual string DefinitionName { get; set; }
    public virtual string DefinitionType { get; set; }
}

public class MetaDataLookup {
    public virtual string Type { get; set; }
    public virtual string LookupKey { get; set; }
    public virtual string LookupValue { get; set; }

    public override bool Equals(object obj) { ... }
    public over int GetHashCode() { ... }
}

public class MetaDataMap : ClassMap<MetaData> {
    public MetaDataMap() {
        Table("PPOMetaData");
        CompositeId()
            .KeyProperty(x => x.TableID, "TableID")
            .KeyProperty(x => x.DefinitionID, "DefinitionID");

        References(x => x.Defintion, "DefinitionID").Not.LazyLoad().Cascade.All().Fetch.Join();
        Map(x => x.TableID);
        Map(x => x.DataValue);
    }
}
public class MetaDataDefinitionMap : ClassMap<MetaDataDefinition> {
    public MetaDataDefinitionMap() {
        Table("MetaDataDefinitions");
        Id(x => x.ID);
        Map(x => x.DefinitionName);
        Map(x => x.Type);
    }
}

public class MetaDataLookupMap : ClassMap<MetaDataLookup> {
    public MetaDataLookupMap() {
        CompositeId()
            .KeyProperty(x => x.LookupType)
            .KeyProperty(x => x.LookupKey);
        Map(x => x.LookupValue);
    }
}

Ideally, I want to have it run a query similar to this:

SELECT     data.TableID, data.DefinitionID, def.DefinitionName, data.DataValue,lu.LookupValue AS DataValue
FROM         dbo.PPOMetadata AS data 
    INNER JOIN dbo.MetaDataDefinitions AS def ON def.ID = data.DefinitionID 
    LEFT OUTER JOIN dbo.MetaDataLookup AS lu ON lu.LookupType = def.Type AND lu.LookupKey = data.DataValue
WHERE data.TableID = 1

In terms of update ability, the only thing I would ever create, update or delete would be in the MetaData table. The definitions and Lookup values would never change (at least from this part of the application). Is mapping the "MetaDataLookup" directly to the MetaData model possible? If so, can someone point me in the right direction of what I should be looking at?

Thanks!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

靖瑶 2024-10-30 00:58:31

我想出了一个似乎有效的解决方法,并且可能会消除一些复杂性。我没有尝试处理 ClassMap 中的复杂连接,而是在 Sql Server 中构建了一个视图来为我完成此操作。在我的应用程序中,我为视图构建了一个新的模型和类映射。我还没有实现任何更新逻辑,但我想我会让更新逻辑直接在 MetaData 模型上工作,而读取逻辑(需要将所有内容连接在一起)将使用新的 MetaDataView 模型。

我仍然很好奇像这样的复杂连接是否可以在 Fluent NHibernate 中实现,但目前这个解决方案似乎对我有用。

I came up with a workaround that seems to be working and might take some of the complexity out. Instead of trying to handle the complex joins in a ClassMap, I built a view in Sql Server that does this for me. In my application, I built a new Model and ClassMap for the view. I haven't implemented any update logic yet, but I think I'll have the update logic work directly on the MetaData model, while the read logic (which needs everything joined together) will use the new MetaDataView model.

I'm still curious if complex joins like this are possible in Fluent NHibernate, but for now this solution seems to be working for me.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文