AndroidStudio修改错误Actual value of parameter 'baudrate' is always 'ComInfo.COM_BAUD_RATE'

在Android Studio中，如果你遇到参数 'baudrate' 的实际值始终是 'ComInfo.COM_BAUD_RATE' 的错误，这可能是因为你在使用该参数时没有正确设置实际的值。

首先，确保你在代码中给 'baudrate' 参数分配了正确的值。你可以使用以下代码示例来设置实际的 'baudrate' 值：

int baudrate = ComInfo.COM_BAUD_RATE;

确保 'ComInfo.COM_BAUD_RATE' 是一个正确的常量，并且它的值是你所需的波特率。

如果你已经正确设置了 'baudrate' 的值，但仍然收到该错误，请检查 'ComInfo.COM_BAUD_RATE' 常量是否被其他代码修改。如果是这样，你需要找到并修复修改 'ComInfo.COM_BAUD_RATE' 值的代码。

另外，还要确保你在使用 'baudrate' 参数时没有意外地重新分配了它的值。请检查代码中是否有对 'baudrate' 的额外赋值语句。

如果以上步骤都没有解决问题，你可以尝试清理和重建你的项目。有时候，错误可能是由于编译器缓存或其他构建问题引起的。

希望这些提示对帮助你解决问题有所帮助！如果还有其他问题，请随时提问。

相关问题

SELECT bs.sample_id, bs.item_id, bs.report_id, bs.order_no, bs.order_id, bs.order_business_type, bs.commission_date, bs.customer_name, bs.applicant, bs.phone, bs.receive_user_name, bs.contract_no, bs.special_requirements, bs.report_org_name, bs.report_org_address, bs.sample_name, bs.standard_instrument_name, bs.complete_day, bs.sample_remark AS remark, bs.standard_instrument_id, bs.sample_no, bs.factory_number, bs.item_name, /*bs.item_quantity,*/ bs.inspection_type, bs.mandatory_flag, bs.test_quantity, bs.sample_state, bs.current_site, bs.plan_complete_date, bs.affix, bs.ranges, bs.grade, bs.factory, bs.calibrat_point, bs.apply_dept, bs.specification, bs.final_fee, bs.service_type, CASE WHEN bs.actual_complete_date IS NOT NULL THEN DATEDIFF( bs.plan_complete_date, bs.actual_complete_date ) ELSE datediff( bs.plan_complete_date, now()) END AS surplus_days, bs.report_no, bs.is_report_back, bs.back_reason AS report_back_reason, bs.is_just_certificate, bs.report_state, bs.temper, bs.humidity, bs.test_result, bs.test_date, bs.next_test_date, bs.test_cycle, bs.test_address, bs.generate_time, bs.point_report_id, bs.is_merge, bs.circulation_flag, bs.item_proposal_fee AS proposal_fee, bs.change_price_reason, bs.test_user_name, bs.group_id, bs.group_name, bs.charging_num, bs.other_fee, bs.receivable_fee, bs.affix_quantity, bs.test_org, bs.out_org_order_no, bs.out_org_sample_no, bs.business_user_name, bs.pdf_path, bs.settlement_state, bs.result_describe, bsa.attach_id FROM view_sample_info bs JOIN bus_sample_report bsr ON bs.report_id = bsr.id JOIN bus_sample sa ON bsr.sample_id = sa.id JOIN bus_sample_attr bsa ON sa.id = bsa.id 根据bs.commission_date 进行排序最近的排上面 bs.commission_date

你可以使用 `ORDER BY` 子句根据 `bs.commission_date` 字段进行排序，以将最近的日期排在前面。以下是示例代码：

SELECT
    bs.sample_id,
    bs.item_id,
    bs.report_id,
    bs.order_no,
    bs.order_id,
    bs.order_business_type,
    bs.commission_date,
    bs.customer_name,
    bs.applicant,
    bs.phone,
    bs.receive_user_name,
    bs.contract_no,
    bs.special_requirements,
    bs.report_org_name,
    bs.report_org_address,
    bs.sample_name,
    bs.standard_instrument_name,
    bs.complete_day,
    bs.sample_remark AS remark,
    bs.standard_instrument_id,
    bs.sample_no,
    bs.factory_number,
    bs.item_name,
    /*bs.item_quantity,*/
    bs.inspection_type,
    bs.mandatory_flag,
    bs.test_quantity,
    bs.sample_state,
    bs.current_site,
    bs.plan_complete_date,
    bs.affix,
    bs.ranges,
    bs.grade,
    bs.factory,
    bs.calibrat_point,
    bs.apply_dept,
    bs.specification,
    bs.final_fee,
    bs.service_type,
    CASE
        WHEN bs.actual_complete_date IS NOT NULL THEN
            DATEDIFF(bs.plan_complete_date, bs.actual_complete_date)
        ELSE
            DATEDIFF(bs.plan_complete_date, now())
        END AS surplus_days,
    bs.report_no,
    bs.is_report_back,
    bs.back_reason AS report_back_reason,
    bs.is_just_certificate,
    bs.report_state,
    bs.temper,
    bs.humidity,
    bs.test_result,
    bs.test_date,
    bs.next_test_date,
    bs.test_cycle,
    bs.test_address,
    bs.generate_time,
    bs.point_report_id,
    bs.is_merge,
    bs.circulation_flag,
    bs.item_proposal_fee AS proposal_fee,
    bs.change_price_reason,
    bs.test_user_name,
    bs.group_id,
    bs.group_name,
    bs.charging_num,
    bs.other_fee,
    bs.receivable_fee,
    bs.affix_quantity,
    bs.test_org,
    bs.out_org_order_no,
    bs.out_org_sample_no,
    bs.business_user_name,
    bs.pdf_path,
    bs.settlement_state,
    bs.result_describe,
    bsa.attach_id
FROM
    view_sample_info bs
    JOIN bus_sample_report bsr ON bs.report_id = bsr.id
    JOIN bus_sample sa ON bsr.sample_id = sa.id
    JOIN bus_sample_attr bsa ON sa.id = bsa.id
ORDER BY
    bs.commission_date DESC;

在上述 SQL 查询中，我们添加了 `ORDER BY` 子句，并使用 `bs.commission_date DESC` 来按照 `bs.commission_date` 字段降序排列结果。这将把最近的日期放在前面。如果你想升序排列，可以使用 `ASC` 关键字，如 `bs.commission_date ASC`。

java.sql.SQLException: sql injection violation, syntax error: TODO : pos 872, line 15, column 43, token UNION : SELECT asewo.code_s as code,asewo.order_type_s as orderType,asewo.equipment_name_s as equipmentName,asewo.executor_s as executor, asewo.plan_start_time_T as planStartTime,asewo.plan_finish_time_T as planFinishTime,asewo.tpm_key_s as tpmKey,asewo.shop_s as shop, asewo.line_S as line,asewo.actual_start_time_t as startTime,asewo.actual_finish_time_t as finishTime,asewo.executor_account_s as executorAccounts, asewo.source_type_s as sourceType,asewo.SOURCE_ORDER_S as sourceOrder,asewo.CREATION_TIME as creationTime FROM AT_AS_EM_Work_Order asewo WHERE to_char(asewo.plan_start_time_T,'yyyy_mm-dd hh24:mi') <= to_char(plan_finish_time_T,'yyyy_mm_dd hh24:mi') AND asewo.ORDER_STATUS_S='创建' AND asewo.executor_s=? ORDER BY asewo.creation_time DESC Union All SELECT asewo.code_s as code,asewo.order_type_s as orderType,asewo.equipment_name_s as equipmentName,asewo.executor_s as executor, asewo.plan_start_time_T as planStartTime,asewo.plan_finish_time_T as planFinishTime,asewo.tpm_key_s as tpmKey,asewo.shop_s as shop, asewo.line_S as line,asewo.actual_start_time_t as startTime,asewo.actual_finish_time_t as finishTime,asewo.executor_account_s as executorAccounts, asewo.source_type_s as sourceType,asewo.SOURCE_ORDER_S as sourceOrder,asewo.CREATION_TIME as creationTime FROM AT_AS_EM_Work_Order asewo WHERE asewo.ORDER_STATUS_S='创建' AND asewo.executor_s=? ORDER BY asewo.creation_time DESC如何改

这段代码是一个SQL查询语句，其中包含了一个UNION操作符，因此可能存在SQL注入漏洞。如果要避免注入漏洞，可以使用参数化查询来构建SQL语句。具体来说，可以将查询中的变量使用占位符（如？）代替，然后在执行查询时将变量的值传递给占位符。这样可以确保输入的变量不会被当做SQL语句的一部分来解释，从而避免注入攻击。

以下是一个使用参数化查询的示例代码：

String sql = "SELECT asewo.code_s as code,asewo.order_type_s as orderType,asewo.equipment_name_s as equipmentName,asewo.executor_s as executor, "
           + "asewo.plan_start_time_T as planStartTime,asewo.plan_finish_time_T as planFinishTime,asewo.tpm_key_s as tpmKey,asewo.shop_s as shop, "
           + "asewo.line_S as line,asewo.actual_start_time_t as startTime,asewo.actual_finish_time_t as finishTime,asewo.executor_account_s as executorAccounts, "
           + "asewo.source_type_s as sourceType,asewo.SOURCE_ORDER_S as sourceOrder,asewo.CREATION_TIME as creationTime "
           + "FROM AT_AS_EM_Work_Order asewo "
           + "WHERE to_char(asewo.plan_start_time_T,'yyyy_mm-dd hh24:mi') <= to_char(plan_finish_time_T,'yyyy_mm_dd hh24:mi') "
           + "AND asewo.ORDER_STATUS_S='创建' "
           + "AND asewo.executor_s=? "
           + "ORDER BY asewo.creation_time DESC "
           + "UNION All "
           + "SELECT asewo.code_s as code,asewo.order_type_s as orderType,asewo.equipment_name_s as equipmentName,asewo.executor_s as executor, "
           + "asewo.plan_start_time_T as planStartTime,asewo.plan_finish_time_T as planFinishTime,asewo.tpm_key_s as tpmKey,asewo.shop_s as shop, "
           + "asewo.line_S as line,asewo.actual_start_time_t as startTime,asewo.actual_finish_time_t as finishTime,asewo.executor_account_s as executorAccounts, "
           + "asewo.source_type_s as sourceType,asewo.SOURCE_ORDER_S as sourceOrder,asewo.CREATION_TIME as creationTime "
           + "FROM AT_AS_EM_Work_Order asewo "
           + "WHERE asewo.ORDER_STATUS_S='创建' "
           + "AND asewo.executor_s=? "
           + "ORDER BY asewo.creation_time DESC";

PreparedStatement stmt = connection.prepareStatement(sql);
stmt.setString(1, executor);
stmt.setString(2, executor);
ResultSet rs = stmt.executeQuery();

在上面的代码中，使用`PreparedStatement`来创建查询语句，并将占位符替换为变量。然后可以使用`setString`等方法来设置变量的值，最后执行查询并获取结果。通过使用参数化查询，可以有效地避免SQL注入漏洞。