Resource.Resource_zh有红色波浪

Resource.Resource_zh是CSDN自主开发一个资源库，它提供了丰富的中文资源供开发者学习和使用。红色波浪可能表示该资源有一些问题或者需要注意的地方。可能是以下几种情况之一：
1. 资源内容有错误或者不完整：红色波浪可能表示该资源中存在错误的信息或者内容不完整，需要开发者注意并进行修正或者补充。
2. 资源更新较久：红色波浪也可能表示该资源的更新时间较久，可能存在一些过时的信息或者技术，建议开发者在使用时注意验证和参考其他更新的资源。
3. 资源评价较低：红色波浪还可能表示该资源的评价较低，可能存在一些质量问题或者用户反馈不太好，建议开发者在使用前仔细考虑和评估。

相关问题

SELECT a.comm_id, c.Title AS house_keeper_name, ( SELECT build.id FROM erp_base.tb_base_masterdata_resource AS resource INNER JOIN erp_base.tb_base_masterdata_resource AS unit ON unit.id = resource.parent_id INNER JOIN erp_base.tb_base_masterdata_resource AS build ON build.id = unit.parent_id WHERE resource.id = a.resource_id ) AS resource_group, b.resource_type FROM tb_charge_receipts_detail a LEFT JOIN erp_base.tb_base_masterdata_resource b ON a.resource_id = b.id LEFT JOIN erp_base.rf_dictionary c ON b.house_keeper = c.id GROUP BY a.comm_id, c.Title, resource_group, b.resource_type 在mysql中报SELECT list is not in GROUP BY clause and contains nonaggregated column 'erp_charge.a.resource_id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by 如何做sql的修改

根据错误提示，可以尝试修改sql_mode，去掉only_full_group_by，或者添加a.resource_id到GROUP BY子句中，但是这样可能会导致查询结果不准确。为了避免这种情况，可以使用聚合函数来替代a.resource_id，比如使用MAX(a.resource_id)。

修改后的SQL语句如下：

SELECT a.comm_id, c.Title AS house_keeper_name,
(SELECT build.id FROM erp_base.tb_base_masterdata_resource AS resource
INNER JOIN erp_base.tb_base_masterdata_resource AS unit ON unit.id = resource.parent_id
INNER JOIN erp_base.tb_base_masterdata_resource AS build ON build.id = unit.parent_id
WHERE resource.id = a.resource_id) AS resource_group,
b.resource_type
FROM tb_charge_receipts_detail a
LEFT JOIN erp_base.tb_base_masterdata_resource b ON a.resource_id = b.id
LEFT JOIN erp_base.rf_dictionary c ON b.house_keeper = c.id
GROUP BY a.comm_id, c.Title, resource_group, b.resource_type

优化sql：SELECT we.organization_id ,we.wip_entity_id ,case when wl.line_id is null then we.wip_entity_name else '' end wip_entity_name ,we.primary_item_id ,mtt.transaction_type_name ,mmt.transaction_date ,bd.department_code ,mmt.inventory_item_id ,mmt.subinventory_code ,mta.reference_account ,br.resource_code ,lu2.meaning as line_type_name ,mta.base_transaction_value ,mta.cost_element_id ,flv.meaning as cost_element ,wdj.class_code job_type_code ,ml.meaning job_type_name FROM (select * from gerp.mtl_material_transactions where substr(transaction_date,1,7) >= '2023-06' and transaction_source_type_id = 5) mmt inner join gerp.wip_entities we on mmt.organization_id = we.organization_id inner join gerp.mtl_transaction_accounts mta on mta.transaction_source_id = we.wip_entity_id and mta.transaction_id = mmt.transaction_id and mta.transaction_source_type_id = 5 inner join gerp.mtl_transaction_types mtt on mtt.transaction_type_id = mmt.transaction_type_id inner join mfg_lookups lu2 on lu2.lookup_code = mta.accounting_line_type and lu2.lookup_type = 'CST_ACCOUNTING_LINE_TYPE' inner join gerp.mtl_system_items_b msi on msi.inventory_item_id = mmt.inventory_item_id and msi.organization_id = mta.organization_id left join gerp.bom_departments bd on bd.department_id = mmt.department_id left join gerp.bom_resources br on br.resource_id = mta.resource_id left join gerp.wip_lines wl on wl.line_id = mmt.repetitive_line_id left join gerp.wip_discrete_jobs wdj on wdj.wip_entity_id = mta.transaction_source_id left join gerp.fnd_lookup_values_vl flv on cast(mta.cost_element_id as string) = flv.lookup_code and flv.lookup_type = 'CST_COST_CODE_TYPE' left join mfg_lookups ml on ml.lookup_code = wdj.job_type and ml.lookup_type = 'WIP_DISCRETE_JOB' 。其中mmt,we,mta,msi,wdj数据量很大

针对这个SQL语句，可以优化的地方有：

1. 使用JOIN语句时，可以根据数据量大小，将数据量大的表放在后面，这样可以避免在连接时出现性能问题。

2. 使用子查询时，可以在子查询中添加条件筛选，减少返回的数据量。

3. 可以对查询中的日期条件进行优化，例如使用日期范围查询时，可以使用BETWEEN关键字代替大于等于和小于等于的运算符。

4. 可以对大表进行分区或分片，以加快查询速度。

5. 可以对JOIN语句中的字段添加索引，以提高查询效率。

下面是对原SQL语句的优化：

SELECT 
    we.organization_id, 
    we.wip_entity_id, 
    CASE WHEN wl.line_id is null THEN we.wip_entity_name ELSE '' END wip_entity_name,
    we.primary_item_id, 
    mtt.transaction_type_name, 
    mmt.transaction_date, 
    bd.department_code, 
    mmt.inventory_item_id, 
    mmt.subinventory_code, 
    mta.reference_account, 
    br.resource_code, 
    lu2.meaning as line_type_name,
    mta.base_transaction_value, 
    mta.cost_element_id, 
    flv.meaning as cost_element, 
    wdj.class_code job_type_code, 
    ml.meaning job_type_name 
FROM 
    gerp.wip_entities we 
    INNER JOIN (
        SELECT 
            * 
        FROM 
            gerp.mtl_material_transactions 
        WHERE 
            transaction_date BETWEEN '2023-06-01' AND '2023-06-30' 
            AND transaction_source_type_id = 5
    ) mmt ON mmt.organization_id = we.organization_id 
    INNER JOIN gerp.mtl_transaction_accounts mta ON mta.transaction_source_id = we.wip_entity_id 
        AND mta.transaction_id = mmt.transaction_id 
        AND mta.transaction_source_type_id = 5 
    INNER JOIN gerp.mtl_transaction_types mtt ON mtt.transaction_type_id = mmt.transaction_type_id 
    INNER JOIN mfg_lookups lu2 ON lu2.lookup_code = mta.accounting_line_type AND lu2.lookup_type = 'CST_ACCOUNTING_LINE_TYPE' 
    INNER JOIN gerp.mtl_system_items_b msi ON msi.inventory_item_id = mmt.inventory_item_id 
        AND msi.organization_id = mta.organization_id 
    LEFT JOIN gerp.bom_departments bd ON bd.department_id = mmt.department_id 
    LEFT JOIN gerp.bom_resources br ON br.resource_id = mta.resource_id 
    LEFT JOIN gerp.wip_lines wl ON wl.line_id = mmt.repetitive_line_id 
    LEFT JOIN gerp.wip_discrete_jobs wdj ON wdj.wip_entity_id = mta.transaction_source_id 
    LEFT JOIN gerp.fnd_lookup_values_vl flv ON cast(mta.cost_element_id as string) = flv.lookup_code 
        AND flv.lookup_type = 'CST_COST_CODE_TYPE' 
    LEFT JOIN mfg_lookups ml ON ml.lookup_code = wdj.job_type AND ml.lookup_type = 'WIP_DISCRETE_JOB';

在优化后的SQL语句中，将子查询中的日期范围查询放在了WHERE语句中，将数据量较大的表放在了后面，左连接的表也放在了后面。同时，可以根据具体情况对需要添加索引的字段进行索引优化。