Sql 从用户查询返回的行不正确
对于SQLs,我是一个新手,在这方面我需要一些帮助,这对我来说有点太复杂了,无法消化和使其工作。我这里有一个存储过程,当客户端输入搜索参数时,它将为客户端显示一个报告 我的表格如下:Sql 从用户查询返回的行不正确,sql,sql-server,database,join,stored-procedures,Sql,Sql Server,Database,Join,Stored Procedures,对于SQLs,我是一个新手,在这方面我需要一些帮助,这对我来说有点太复杂了,无法消化和使其工作。我这里有一个存储过程,当客户端输入搜索参数时,它将为客户端显示一个报告 我的表格如下: TXN_RMReport-RMRID(主键)、rmrPlant(fk,来自FO_财产)、rmrCID(fk,来自RM_类别)、rmrBusinessArea、rmrCostCenter、rmrWCCode、RMRRreportedby FO_属性-PID(主键)、pCode、pMappingCode(包含RM_业务
+------+------+---------+-------------+------------+--------------+-------------+
| Code | Area | CCenter | DESCRIPTION | ReportedBy | Remarks | CreatedDate |
+------+------+---------+-------------+------------+--------------+-------------+
| RWB | FB | 200 | CTERRACE | TANTAN | NO CAKE | 20/01/2017 |
| RWB | FB | 200 | FAVENUE | TANTAN | NO CAKE | 20/01/2017 |
| RWMS | CS | 501 | BACCARAT | JIM | SCRATCHED | 20/01/2017 |
| RWB | ADMC | 700 | CAFETERIA | JIM | BROKEN TILES | 21/01/2017 |
| RWB | ADMC | 700 | HRESOURCE | JIM | BROKEN TILES | 21/01/2017 |
| RWMS | FB | 200 | CTERRACE | ELSA | LEAKING PIPE | 20/01/2017 |
| RWMS | FB | 200 | FAVENUE | ELSA | LEAKING PIPE | 20/01/2017 |
+------+------+---------+-------------+------------+--------------+-------------+
预期结果:
+------+------+---------+-------------+------------+--------------+-------------+
| Code | Area | CCenter | DESCRIPTION | ReportedBy | Remarks | CreatedDate |
+------+------+---------+-------------+------------+--------------+-------------+
| RWB | FB | 200 | CTERRACE | TANTAN | NO CAKE | 20/01/2017 |
| RWMS | CS | 501 | BACCARAT | JIM | SCRATCHED | 20/01/2017 |
| RWB | ADMC | 700 | CAFETERIA | JIM | BROKEN TILES | 21/01/2017 |
| RWMS | FB | 200 | FAVENUE | ELSA | LEAKING PIPE | 20/01/2017 |
+------+------+---------+-------------+------------+--------------+-------------+
通常最好在WHERE子句中使用和/或而不是大小写表达式。请以文本格式提供表架构、测试数据和所需结果。关于如何提出好问题,请参考以下链接它们不是DUP-行是不同的。左侧部分有指向不同RMCostCenter的链接。这意味着您有多行具有相同的rmrplant和不同的成本中心。谁在增加你的行数-我不知道。RM_BusinessArea可能是。@Ivan Starostin我几乎可以肯定这里的问题表是RM_成本中心,因为相同的代码如“200”、“500”和“701”显示两次,只是它们有不同的描述和指向不同属性代码的链接,如“RWB”和“RWMS”,或“ADMC”到“EWB”.那你为什么要用非唯一的ccCostCenter而不是CCID(pk)加入?
+------+------+---------+-------------+------------+--------------+-------------+
| Code | Area | CCenter | DESCRIPTION | ReportedBy | Remarks | CreatedDate |
+------+------+---------+-------------+------------+--------------+-------------+
| RWB | FB | 200 | CTERRACE | TANTAN | NO CAKE | 20/01/2017 |
| RWB | FB | 200 | FAVENUE | TANTAN | NO CAKE | 20/01/2017 |
| RWMS | CS | 501 | BACCARAT | JIM | SCRATCHED | 20/01/2017 |
| RWB | ADMC | 700 | CAFETERIA | JIM | BROKEN TILES | 21/01/2017 |
| RWB | ADMC | 700 | HRESOURCE | JIM | BROKEN TILES | 21/01/2017 |
| RWMS | FB | 200 | CTERRACE | ELSA | LEAKING PIPE | 20/01/2017 |
| RWMS | FB | 200 | FAVENUE | ELSA | LEAKING PIPE | 20/01/2017 |
+------+------+---------+-------------+------------+--------------+-------------+
+------+------+---------+-------------+------------+--------------+-------------+
| Code | Area | CCenter | DESCRIPTION | ReportedBy | Remarks | CreatedDate |
+------+------+---------+-------------+------------+--------------+-------------+
| RWB | FB | 200 | CTERRACE | TANTAN | NO CAKE | 20/01/2017 |
| RWMS | CS | 501 | BACCARAT | JIM | SCRATCHED | 20/01/2017 |
| RWB | ADMC | 700 | CAFETERIA | JIM | BROKEN TILES | 21/01/2017 |
| RWMS | FB | 200 | FAVENUE | ELSA | LEAKING PIPE | 20/01/2017 |
+------+------+---------+-------------+------------+--------------+-------------+