3

我们最近开始使用 ServiceStack AutoQuery。这是一个不错的功能，我们非常喜欢它。我们有一个这样的表结构（缩小版以便于阅读）：

Salary [Id (PK), ManagerId (FK)] 
Manager [Id (PK), DepartmentId (FK)] /* Manager is like Employee table even thought it's named Manager */
Department [Id (PK), ActiveManagerId (FK)] /* The FK ActiveManagerId is supposed to be a shortcut, it's Nullable.  */

所以理论上我们可以有这样的连接

Salary -> Manager via Salary.ManagerId = Manager.Id
Manager -> Department via Manager.DepartmentId = Department.Id
Department -> Manager via Department.ActiveManagerId = Manager.Id

但是在这种特定情况下，如果我们通过 Department.ActiveManagerId = Manager.Id 从 Department 加入到 Manager 将不会产生正确的结果，因为 Department.ActiveManagerId 是一个快捷方式，是为其他场景设计的。

所以当我像这样定义 AutoQuery

public class SalaryQuery : QueryBase<Salary, SalaryQueryResult>,
 ILeftJoin<Salary, Manager, Department>

下面的 SQL 由 AutoQuery 生成，从 ServiceStack AutoQuery 的角度来看是正确的。

select  s.Id
    ,   d.Id
from    Salary s
    left join
        Manager m
    on  s.ManagerId = m.Id
    left join
        Department d
    on  d.ActiveManagerId = m.Id /* should NOT use shortcut: Department -> Manager via Department.ActiveManagerId = Manager.Id */

但相反，我们希望能够生成如下所示的 SQL

select  s.Id
    ,   d.Id
from    Salary s
    left join
        Manager m
    on  s.ManagerId = m.id
    left join
        Department d
    on  d.Id = m.DepartmentId /* should use the desired FK: Manager -> Department via Manager.DepartmentId = Department.Id */
4

1 回答 1

3

如果您想要不同的 JOIN 行为，则需要在Custom AutoQuery implementation中添加自定义 LEFT JOIN ，例如：

//AutoQuery DTO
public class SalaryQuery : QueryDb<Salary,SalaryQueryResult>, ILeftJoin<Salary,Manager>

//Implementation
public class MyServices : Service
{
    public IAutoQueryDb AutoQuery { get; set; }

    public object Any(SalaryQuery query)
    {
        var q = AutoQuery.CreateQuery(query, base.Request)
            .LeftJoin<Manager, Department>((m, d) => d.Id == m.DepartmentId);

        return AutoQuery.Execute(query, q);
    } 
}

注意：从 v4.0.56QueryBase<T>开始，已弃用并重命名为 QueryDb。

于 2016-05-02T07:03:00.793 回答