为什么下面的sql语句会输出重复的结果:SELECT tp.parent_production_orders AS parent_production_orders, tp.production_orders AS production_orders, tp.work_order AS work_order, tp.contract AS contract, tp.sbbh AS sbbh, tp.batch_num AS batch_num, tp.product_code AS product_code, tp.product_number AS product_number, tp.product_name AS product_name, to_char( middle.create_date, 'yyyy-mm-dd' ) AS issued_date, to_char( to_timestamp( tp.delivery_time / 1000 ), 'yyyy-mm-dd' ) AS delivery_time, middle.line_code AS work_area_code, middle.line_name AS work_area_name, tp.workorder_number AS workorder_number, tp.complete_number AS complete_number, tp.part_unit AS part_unit, middle.work_time_type AS work_time_type, middle.process_time AS process_time, CASE WHEN sc.totalSubmitHours IS NULL THEN 0 ELSE sc.totalSubmitHours END AS submit_work_hours, CASE WHEN middle.process_time > 0 AND sc.totalSubmitHours IS NOT NULL THEN round( ( sc.totalSubmitHours / middle.process_time ), 2 ) * 100 ELSE 0 END plan_achievement_rate, CASE WHEN sc.totalSubmitHours IS NULL THEN 0 ELSE round( CAST ( sc.totalSubmitHours AS NUMERIC ) / CAST ( 60 AS NUMERIC ), 1 ) END AS submit_work_hours_h, round( CAST ( middle.process_time AS NUMERIC ) / CAST ( 60 AS NUMERIC ), 1 ) AS process_time_h, pinfo.material_channel AS material_channel FROM hm_model_work_order_report_middle middle LEFT JOIN hm_model_trc_plan tp ON middle.work_order = tp.work_order LEFT JOIN ( SELECT oro.work_order AS orderNo, oro.work_area_code AS lineCode, SUM ( submit_work_hours ) AS totalSubmitHours, '自制' AS workHourType FROM hm_model_trc_order_report_operation_u orou LEFT JOIN hm_model_trc_order_report_operation oro ON orou.work_order_process_id = oro.ID WHERE orou.work_order_process_id IS NOT NULL AND oro.work_area_code IS NOT NULL GROUP BY oro.work_order, oro.work_area_code UNION all SELECT ohs.work_order_no AS orderNo, ohs.line_code AS lineCode, SUM ( receiving_hour ) AS totalSubmitHours, '外委' AS workHourType FROM hm_model_outsourcing_hour_statistics ohs GROUP BY ohs.work_order_no, ohs.line_code ) sc ON middle.work_order = sc.orderNo AND middle.line_code = sc.lineCode AND middle.work_time_type = sc.workHourType LEFT JOIN hm_model_part_info AS pinfo ON tp.product_number = pinfo.part_code WHERE middle.process_time > 0 AND tp.delivery_time IS NOT NULL AND tp.production_orders LIKE'FJ2023051100286' ORDER BY to_char( to_timestamp( tp.delivery_time / 1000 ), 'yyyy-mm-dd' ) DESC, tp.parent_production_orders DESC, tp.node_level ASC

时间: 2024-04-27 11:20:03 浏览: 10
可能是因为查询结果中有多个相同的记录,即存在多个记录的各个字段的值都相同,因此会出现重复的结果。可以使用 DISTINCT 关键字去除重复的记录。例如:SELECT DISTINCT tp.parent_production_orders AS parent_production_orders, tp.production_orders AS production_orders, ... (省略后面的 SQL 语句)。另外,还可以检查查询条件是否合理,是否需要增加更多的条件来过滤数据。
相关问题

一下SQL语句有错吗:select p.product_name , s.year , s.price from Sales as s left join Product as p where s.product_id = p.product_id;

这个 SQL 语句有误,应该在 left join 后面指定关联条件,如下所示: ``` SELECT p.product_name, s.year, s.price FROM Sales AS s LEFT JOIN Product AS p ON s.product_id = p.product_id; ``` 在这个语句中,我们使用 ON 子句来指定关联条件,连接 Sales 表和 Product 表的 product_id 列。这样就可以正确地将每个销售记录与其对应的产品名称关联起来,同时在没有匹配产品的情况下也可以保留销售记录。

select Customers.cust_name,Orders.oder_num from Customers inner join Orders on Customers.cust_id == Orders.cust_id order by Customers.cust_name desc这句SQL有什么语法错误

这句 SQL 语句看起来是正确的,但是有一个小错误。在 SQL 中,"==" 不是用于比较相等的运算符,而是 " = "。因此,正确的 SQL 语句应该是: ```sql SELECT Customers.cust_name, Orders.oder_num FROM Customers INNER JOIN Orders ON Customers.cust_id = Orders.cust_id ORDER BY Customers.cust_name DESC ``` 这将按照顾客的名称(以降序排列)和订单号选择顾客和订单信息,并将它们结合在一起。

相关推荐

将下面这条sql语句简短一些:SELECT * FROM ( SELECT fpd.fpd_id AS fpdId, fpd.fpd_budget_project AS fpdBudgetProject, fpd.fpd_budget_project_id AS fpdBudgetProjectId, fpd.fpd_pf_name AS fpdPfName, fpd.fpd_pf_id AS fpdPfId, fpd.fpd_expend_subject AS fpdExpendSubject, fpd.fpd_expend_subject_id AS fpdExpendSubjectId, fpd.fpd_payee_name AS fpdPayeeName, fpd.fpd_payee_account AS fpdPayeeAccount, fpd.fpd_payee_opening_bank AS fpdPayeeOpeningBank, fpd.fpd_payee_opening_bank_num AS fpdPayeeOpeningBankNum, fpd.fpd_dept_pay_economics_classify_num AS fpdDeptPayEconomicsClassifyNum, fpd.fpd_dept_pay_economics_classify_name AS fpdDeptPayEconomicsClassifyName, fpd.fpd_applied_amount AS fpdAppliedAmount, fpd.fpd_capital_use AS fpdCapitalUse, fpd.fpd_postscript AS fpdPostscript, fpd.fpd_budget_item_name AS fpdBudgetItemName, fpd.fpd_budget_item_number AS fpdBudgetItemNumber, fpd.fpd_dr_name AS fpdDrName, dbec.dbec_parent_num AS dbecParentNum FROM financial_payment_details fpd LEFT JOIN dept_budget_economy_class dbec ON fpd.fpd_dept_pay_economics_classify_num = dbec.dbec_num WHERE fpd.fpd_is_tax = "0" UNION ALL SELECT fpd.fpd_id AS fpdId, fpd.fpd_budget_project AS fpdBudgetProject, fpd.fpd_budget_project_id AS fpdBudgetProjectId, fpd.fpd_pf_name AS fpdPfName, fpd.fpd_pf_id AS fpdPfId, fpd.fpd_expend_subject AS fpdExpendSubject, fpd.fpd_expend_subject_id AS fpdExpendSubjectId, fpd.fpd_payee_name AS fpdPayeeName, fpd.fpd_payee_account AS fpdPayeeAccount, fpd.fpd_payee_opening_bank AS fpdPayeeOpeningBank, fpd.fpd_payee_opening_bank_num AS fpdPayeeOpeningBankNum, fpd.fpd_dept_pay_economics_classify_num AS fpdDeptPayEconomicsClassifyNum, fpd.fpd_dept_pay_economics_classify_name AS fpdDeptPayEconomicsClassifyName, sum( fpd.fpd_applied_amount ) AS fpdAppliedAmount, fpd.fpd_capital_use AS fpdCapitalUse, fpd.fpd_postscript AS fpdPostscript, fpd.fpd_budget_item_name AS fpdBudgetItemName, fpd.fpd_budget_item_number AS fpdBudgetItemNumber, fpd.fpd_dr_name AS fpdDrName, dbec.dbec_parent_num AS dbecParentNum FROM financial_payment_details fpd LEFT JOIN dept_budget_economy_class dbec ON fpd.fpd_dept_pay_economics_classify_num = dbec.dbec_num WHERE fpd.fpd_is_tax = "1" GROUP BY fpd_pay_num ) t1

第一个SQL: SELECT orders.id,orders.user_id,orders.cityarea_id,orders.batchcode,orders.status, orders.pay_status,orders.real_pay,orders.total,orders.money,orders.pay_type, orders.premium,orders.createtime,orders.paytime,orders.confirmtime, orders.is_evaluate,orders.pay_method,orders.exp_user_id, orders.return_score, orders.is_change,orders.reward_money,orders.isvalid,orders.after_sale_status,orders.remark, orders.use_coupon_detail,orders.block_chain_price, users.name,users.weixin_name,users.weixin_fromuser, users.phone,wcoe.diy_area_name from wsy_o2o.weixin_cityarea_orders orders left join wsy_o2o.weixin_cityarea_supply supply on orders.cityarea_id = supply.id left join wsy_o2o.weixin_cityarea_payonline_orders wcco on orders.batchcode=wcco.batchcode left join wsy_user.weixin_users users on users.id = orders.user_id LEFT JOIN wsy_o2o.weixin_cityarea_orders_extend wcoe ON orders.batchcode = wcoe.batchcode WHERE orders.types=3 and orders.customer_id = 41 AND orders.isvalid=true GROUP BY orders.batchcode ORDER BY orders.id DESC limit 0,20; 第二个SQL: SELECT orders.id,orders.user_id,orders.cityarea_id,orders.batchcode,orders.status, orders.pay_status,orders.real_pay,orders.total,orders.money,orders.pay_type, orders.premium,orders.createtime,orders.paytime,orders.confirmtime, orders.is_evaluate,orders.pay_method,orders.exp_user_id, orders.return_score, orders.is_change,orders.reward_money,orders.isvalid,orders.after_sale_status,orders.remark, orders.use_coupon_detail,orders.block_chain_price, users.name,users.weixin_name,users.weixin_fromuser, users.phone,wcoe.diy_area_name ,writes.ActivityStatus,writes.NewMoney from wsy_o2o.weixin_cityarea_orders orders left join wsy_o2o.weixin_cityarea_supply supply on orders.cityarea_id = supply.id left join wsy_o2o.weixin_cityarea_payonline_orders wcco on orders.batchcode=wcco.batchcode left join wsy_user.weixin_users users on users.id = orders.user_id LEFT JOIN wsy_o2o.weixin_cityarea_orders_extend wcoe ON orders.batchcode = wcoe.batchcode LEFT JOIN wsy_dream.ShopWrite writes on orders.batchcode = writes.Batchcode WHERE orders.types=3 and orders.customer_id = 41 AND orders.isvalid=true GROUP BY orders.batchcode ORDER BY orders.id DESC limit 0,20; 为什么查询结果从0.7秒变成了3.7秒?

最新推荐

recommend-type

MySQL复制出错 Last_SQL_Errno:1146的解决方法

主要介绍了MySQL复制出错 Last_SQL_Errno:1146的解决方法,需要的朋友可以参考下
recommend-type

SQL Server阻止了对组件xp_cmdshell过程的解决方案.docx

SQL Server阻止了对组件xp_cmdshell过程的解决方案。 错误描述:SQL Server阻止了对组件‘xp_cmdshell’的过程‘sys.xp_cmdshell’的访问。因为此组件已作为此服务嚣安全配置的一部分而被关闭。系统管理员可以通过...
recommend-type

深入理解用mysql_fetch_row()以数组的形式返回查询结果

result:由函数mysql_query()或mysql_db_query()返回的结果标识,用来指定所要获取的数据的SQL语句类型。函数返回值如下。成功:一个数组,该数组包含了查询结果集中当前行数据信息,数组下标范围0~记录属性数−1,...
recommend-type

SQL Sever中使用SQL语句实现把重复行数据合并为一行并用逗号分隔

主要介绍了SQL Sever中使用SQL语句实现把重复行数据合并为一行并用逗号分隔,本文给出了两种实现方式,需要的朋友可以参考下
recommend-type

SQLServer中Partition By及row_number 函数使用详解

partition by关键字是分析性函数的一部分,partition by用于给结果集分组,如果没有指定那么它把整个结果集作为一个分组,本文给大家介绍SQLServer中Partition By及row_number 函数使用详解,需要的朋友参考下
recommend-type

zigbee-cluster-library-specification

最新的zigbee-cluster-library-specification说明文档。
recommend-type

管理建模和仿真的文件

管理Boualem Benatallah引用此版本:布阿利姆·贝纳塔拉。管理建模和仿真。约瑟夫-傅立叶大学-格勒诺布尔第一大学,1996年。法语。NNT:电话:00345357HAL ID:电话:00345357https://theses.hal.science/tel-003453572008年12月9日提交HAL是一个多学科的开放存取档案馆,用于存放和传播科学研究论文,无论它们是否被公开。论文可以来自法国或国外的教学和研究机构,也可以来自公共或私人研究中心。L’archive ouverte pluridisciplinaire
recommend-type

实现实时数据湖架构:Kafka与Hive集成

![实现实时数据湖架构:Kafka与Hive集成](https://img-blog.csdnimg.cn/img_convert/10eb2e6972b3b6086286fc64c0b3ee41.jpeg) # 1. 实时数据湖架构概述** 实时数据湖是一种现代数据管理架构,它允许企业以低延迟的方式收集、存储和处理大量数据。与传统数据仓库不同,实时数据湖不依赖于预先定义的模式,而是采用灵活的架构,可以处理各种数据类型和格式。这种架构为企业提供了以下优势: - **实时洞察:**实时数据湖允许企业访问最新的数据,从而做出更明智的决策。 - **数据民主化:**实时数据湖使各种利益相关者都可
recommend-type

2. 通过python绘制y=e-xsin(2πx)图像

可以使用matplotlib库来绘制这个函数的图像。以下是一段示例代码: ```python import numpy as np import matplotlib.pyplot as plt def func(x): return np.exp(-x) * np.sin(2 * np.pi * x) x = np.linspace(0, 5, 500) y = func(x) plt.plot(x, y) plt.xlabel('x') plt.ylabel('y') plt.title('y = e^{-x} sin(2πx)') plt.show() ``` 运行这段
recommend-type

JSBSim Reference Manual

JSBSim参考手册,其中包含JSBSim简介,JSBSim配置文件xml的编写语法,编程手册以及一些应用实例等。其中有部分内容还没有写完,估计有生之年很难看到完整版了,但是内容还是很有参考价值的。