7. 4plan~

最新推荐文章于 2024-06-05 20:45:46 发布
原创 最新推荐文章于 2024-06-05 20:45:46 发布 · 714 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#struts #report

hehe~the task has began ,with elite:)

today plan

1.business ,reading code 

2. bbs struts learning

3.a desiring analyse report~

【保姆级教程附代码】Pytorch (.pth) 到 TensorRT (.plan) 模型转化全流程
weixin_44212848的博客
04-03 2302
那么恭喜你的 .onnx 大概率是可以转化到 .plan 的！当然这里也有些坑，比如明明是显存不够错误，但日志里完全没提 oom，而是说节点问题。。。
wsus.zip_plana4r_scaredneu_windows update_zip_开发wsus
09-21
本压缩包“wsus.zip_plana4r_scaredneu_windows update_zip_开发wsus”可能包含与部署和配置WSUS服务器相关的资源，以帮助IT专业人员更有效地管理其网络中的Windows更新流程。 在开发和维护WSUS时，以下几个关键...
【保姆级教程附代码(二)】Pytorch (.pth) 到 TensorRT (.plan) 模型转化全流程细化
weixin_44212848的博客
05-31 1917
上一篇简要介绍了神经网络模型从到的流程。本文则进一步细化该流程中需要的步骤，包括用到的各种环境和工具。此外，系列文不仅包括了“怎么做”，还包括了“为什么这么做”的个人理解。
1030. Travel Plan (30)
Apie_CZX的专栏
06-24 1304
题目链接：http://www.patest.cn/contests/pat-a-practise/1030 题目： 1030. Travel Plan (30) 时间限制 400 ms 内存限制 65536 kB 代码长度限制 16000 B 判题程序 Standard 作者 CH
oracle plan_table,Oracle -- 深入体会PLAN_TABLE、PLAN_TABLE$
weixin_36164462的博客
04-04 1196
注释PLAN_TABLEisthedefaulttableforresultsoftheEXPLAINPLANstatement.Itiscreatedbyutlxplan.sql,anditcontainsonerowforeachstepintheexecutionplan. --->session1:commit，sess...
Sdp Plan-b UnifiedPlan
jaygno的专栏
05-22 6369
Unified Plan 和 Plan B ...
使用pg_hint_plan固定Postgresql执行计划
InternalsOf
05-27 1674
pg_hint_plan使用教程实例与避坑技巧
Postgresql源码（106）Generic Plan与Custom Plan的区别（以分区表为例）
InternalsOf
06-15 1714
Generic Plan与Custom Plan的区别（以分区表为例）
[论文笔记]Plan-and-Solve Prompting: Improving Zero-Shot Chain-of-Thought Reasoning by Large Language Mod
日积月累，天道酬勤
06-05 1763
⭐ 为了解决思维链应用中的计算错误、缺失推理步骤错误和语义理解错误。作者引入了计划与解决提示策略。引导大语言模型制定一个将整个任务分解为较小子任务的计划，并根据计划执行子任务，从而达到更好的效果。
FloorPlan 经验总结
热门推荐
紫轩阁
12-30 1万+
[讨论] IC layout FloorPlan 经验总结（摘录） 布局前的准备:[52RD.com] 1 查看捕捉点设置是否正确.08工艺为0.1,06工艺为0.05,05工艺为0.025.[52RD.com] 2 Cell名称不能以数字开头.否则无法做DRACULA检查.[52RD.com] 3 布局前考虑好出PIN的方向和位置[52RD.com] 4 布局前分析电路，完成同一功
Project plan.xlsx
10-12
项目计划的创建和执行是项目生命周期的重要环节，通常使用项目管理软件（如Microsoft Project、Smartsheet、Trello等）或电子表格（如Project plan.xlsx）来制定详细的项目计划文档。这些工具能够帮助项目管理者跟踪...
plan_project.zip
03-07
【标题】"plan_project.zip" 是一个包含Spring Boot与Dubbo整合示例代码的压缩包。这个项目旨在帮助开发者理解如何在Spring Boot框架中集成Dubbo服务，以便构建分布式微服务架构。 【描述】提到，这个项目包含了...
IPv6.Address.Planning.Designing.an.Address.Plan.for.the.Future.epub
03-28
If you’re ready to join the move to IPv6, this comprehensive guide gets you started by showing you how to create an effective IPv6 address plan. In three example-driven sections—preparation, design,...
OmniPlan3 3.2.zip
08-27
4. **风险评估**：OmniPlan3具有内置的风险管理功能，允许用户识别潜在问题并进行概率和影响分析，以便提前做好应对策略。 5. **进度跟踪**：实时跟踪项目进度，通过比较实际进度与计划进度，及时发现偏差并进行...
基于GEC6818平台的五子棋人机对战系统设计与实现
11-25
五子棋作为一种广为人知的策略性棋盘游戏，其基本规则易于掌握。在选定人机对战模式后，由程序执黑先行，用户执白应对。双方依次在棋盘上落子，任何一方在横向、纵向或斜向形成连续五个或更多同色棋子即获胜。 项目资源涵盖多个技术领域的程序代码，涉及前后端开发、移动终端应用、操作系统、智能系统、物联网技术、信息管理系统、数据存储方案、硬件设计、大数据处理、教学资料、多媒体处理及网站构建等多个方向。具体技术实例包括嵌入式平台如STM32与ESP8266，编程语言如PHP、QT、C++、Java、Python、C#，系统开发如Linux与iOS，以及电子设计自动化工具和实时操作系统等。 主要技术栈包含服务端开发语言Java、Python及Node.js，后端框架Spring Boot与Django，前端技术React、Angular与Vue，界面设计框架Bootstrap与Material-UI，数据库系统MySQL、PostgreSQL和MongoDB，缓存工具Redis，以及容器化部署方案Docker与Kubernetes。 资源来源于网络分享，仅用于学习交流使用，请勿用于商业，如有侵权请联系我删除！
lv_0_20251125195629.mp4
11-25
lv_0_20251125195629.mp4
numpy、pandas、sklearn、pytorch等数据分析工具的一些使用技巧
11-25
NumPy数组操作实战技巧 numpy、pandas、sklearn、pytorch等数据分析工具的一些使用技巧
中国Cassandra数据库用户组开源社区项目-专注于Apache-Cassandra分布式NoSQL数据库技术研究与实践-提供技术文档下载与源码解析-集成Titan图数据库与Lu.zip
最新发布
11-25
Buffer内存管理实战技巧中国Cassandra数据库用户组开源社区项目_专注于Apache_Cassandra分布式NoSQL数据库技术研究与实践_提供技术文档下载与源码解析_集成Titan图数据库与Lu.zip中国Cassandra数据库用户组开源社区项目_专注于Apache_Cassandra分布式NoSQL数据库技术研究与实践_提供技术文档下载与源码解析_集成Titan图数据库与Lu.zip
图像处理基于电磁学优化算法的多阈值分割算法研究（Matlab代码实现）
11-25
【图像处理】基于电磁学优化算法的多阈值分割算法研究（Matlab代码实现）内容概要：本文研究基于电磁学优化算法（Electromagnetism-like Optimization, EMO）的多阈值图像分割方法，并通过Matlab代码实现。该方法借鉴电磁学中电荷间相互作用的机制，将图像分割问题转化为优化问题，利用EMO算法搜索最优阈值组合，以最大化分割效果的评价指标（如Otsu法或多级别熵）。文中详细介绍了EMO算法的基本原理、实现步骤及其在图像多阈值分割中的具体应用流程，展示了该算法能够有效避免传统方法易陷入局部最优的问题，从而获得更精确的分割结果。; 适合人群：具备图像处理基础知识和Matlab编程能力的高校学生、科研人员及工程技术人员。; 使用场景及目标：①解决复杂背景下图像的多目标分割问题，提升医学影像、遥感图像等领域的分割精度；②学习智能优化算法（如EMO）在图像处理中的实际应用，为研究新型分割算法提供技术参考和实现范例。; 阅读建议：在学习过程中应结合Matlab代码，深入理解EMO算法的寻优机制与图像分割评价函数的构建方法，建议自行调试不同参数对分割效果的影响，以加深对算法性能的理解。
SELECT COALESCE(T8.PROJECT_NO, T1.PROJECT_NO) AS PROJECT_NO, COALESCE(T8.PIPE_NO, T1.PIPE_NO) AS PIPE_NO, COALESCE(T8.PIPE_VERSION, T1.PIPE_VERSION) AS PIPE_VERSION, COALESCE(T8.IS_TOP_VERSION, T3.IS_TOP_VERSION) AS IS_TOP_VERSION, COALESCE(T8.IS_DELETE, T3.IS_DELETE) AS IS_DELETE, COALESCE(T8.IS_PAUSE, T3.IS_PAUSE) AS IS_PAUSE, T3.WEIGHT, T3.INCH, T4.WORK_SPACE_NO cutPlanWorkSpaceNo, T5.WORK_SPACE_NO assyPlanWorkSpaceNo, T6.WORK_SPACE_NO weldingPlanWorkSpaceNo, COALESCE(T8.CUT_PLAN_DATE, T1.CUT_PLAN_DATE) AS CUT_PLAN_DATE, COALESCE(T8.ASSY_PLAN_DATE, T1.ASSY_PLAN_DATE) AS ASSY_PLAN_DATE, COALESCE(T8.WELDING_PLAN_DATE, T1.WELDING_PLAN_DATE) AS WELDING_PLAN_DATE, COALESCE(T8.WELDING_PRE_INSP_PLAN_DATE, T1.WELDING_PRE_INSP_PLAN_DATE) AS WELDING_PRE_INSP_PLAN_DATE, COALESCE(T8.WELDING_POST_INSP_PLAN_DATE, T1.WELDING_POST_INSP_PLAN_DATE) AS WELDING_POST_INSP_PLAN_DATE, COALESCE(T8.IN_BASKET_PLAN_DATE, T1.IN_BASKET_PLAN_DATE) AS IN_BASKET_PLAN_DATE, T7.INST_NEED_DATE, T7.CRAFT_LINE_TYPE, (COALESCE(T8.IN_BASKET_PLAN_DATE, T1.IN_BASKET_PLAN_DATE) - COALESCE(T8.CUT_PLAN_DATE, T1.CUT_PLAN_DATE)) AS PIPE_PRE_CYC FROM CP_PIPE_PLAN_DESP T1 LEFT JOIN CP_PIPE_PLAN T2 ON T1.PLAN_NO = T2.PLAN_NO AND T1.PLAN_VERSION = T2.PLAN_VERSION AND T1.PROJECT_NO = T2.PROJECT_NO AND T2.PLAN_TYPE = '预制' LEFT JOIN CP_PIPE_DESIGN_INFO T3 ON T1.PROJECT_NO = T3.PROJECT_NO AND T1.PIPE_NO = T3.PIPE_NO AND T1.PIPE_VERSION = T3.PIPE_VERSION LEFT JOIN CP_PIPE_PROD_INFO T7 ON T3.PROJECT_NO = T7.PROJECT_NO AND T3.PIPE_NO = T7.PIPE_NO AND T3.PIPE_VERSION = T7.PIPE_VERSION LEFT JOIN CP_WORK_SPACE T4 ON T1.CUT_WORK_SPACE_ID = T4.ID LEFT JOIN CP_WORK_SPACE T5 ON T1.ASSY_WORK_SPACE_ID = T5.ID LEFT JOIN CP_WORK_SPACE T6 ON T1.WELDING_WORK_SPACE_ID = T6.ID LEFT JOIN CP_PIPE_PLAN_ADD_ITEM_EDIT_TEMP T8 ON T1.PLAN_NO = T8.PLAN_NO AND T1.PLAN_VERSION = T8.PLAN_VERSION AND T1.PROJECT_NO = T8.PROJECT_NO AND T1.PIPE_NO = T8.PIPE_NO AND T1.PIPE_VERSION = T8.PIPE_VERSION WHERE T1.PLAN_NO = 'YPH614202511' AND T1.PLAN_VERSION = 6 AND T1.PROJECT_NO = 'H614' AND T2.ORG_NO = 'C000030' UNION ALL SELECT T1.PROJECT_NO, T1.PIPE_NO, T1.PIPE_VERSION, T1.IS_TOP_VERSION, T1.IS_DELETE, T1.IS_PAUSE, T3.WEIGHT, T3.INCH, T4.WORK_SPACE_NO AS cutPlanWorkSpaceNo, T5.WORK_SPACE_NO AS assyPlanWorkSpaceNo, T6.WORK_SPACE_NO AS weldingPlanWorkSpaceNo, T1.CUT_PLAN_DATE, T1.ASSY_PLAN_DATE, T1.WELDING_PLAN_DATE, T1.WELDING_PRE_INSP_PLAN_DATE, T1.WELDING_POST_INSP_PLAN_DATE, T1.IN_BASKET_PLAN_DATE, T7.INST_NEED_DATE AS needDate, T7.CRAFT_LINE_TYPE, (T1.IN_BASKET_PLAN_DATE - T1.CUT_PLAN_DATE) AS PIPE_PRE_CYC FROM CP_PIPE_PLAN_ADD_ITEM_EDIT_TEMP T1 LEFT JOIN CP_PIPE_PLAN T2 ON T1.PLAN_NO = T2.PLAN_NO AND T1.PLAN_VERSION = T2.PLAN_VERSION AND T1.PROJECT_NO = T2.PROJECT_NO AND T2.PLAN_TYPE = '预制' LEFT JOIN CP_PIPE_DESIGN_INFO T3 ON T1.PROJECT_NO = T3.PROJECT_NO AND T1.PIPE_NO = T3.PIPE_NO AND T1.PIPE_VERSION = T3.PIPE_VERSION LEFT JOIN CP_PIPE_PROD_INFO T7 ON T3.PROJECT_NO = T7.PROJECT_NO AND T3.PIPE_NO = T7.PIPE_NO AND T3.PIPE_VERSION = T7.PIPE_VERSION LEFT JOIN CP_WORK_SPACE T4 ON T1.CUT_WORK_SPACE_ID = T4.ID LEFT JOIN CP_WORK_SPACE T5 ON T1.ASSY_WORK_SPACE_ID = T5.ID LEFT JOIN CP_WORK_SPACE T6 ON T1.WELDING_WORK_SPACE_ID = T6.ID WHERE NOT EXISTS (SELECT 1 FROM CP_PIPE_PLAN_DESP T1 WHERE T1.PLAN_NO = T1.PLAN_NO AND T1.PLAN_VERSION = T1.PLAN_VERSION AND T1.PROJECT_NO = T1.PROJECT_NO AND T1.PIPE_NO = T1.PIPE_NO AND T1.PIPE_VERSION = T1.PIPE_VERSION) AND T1.PLAN_NO = 'YPH614202511' AND T1.PLAN_VERSION = 6 AND T1.PROJECT_NO = 'H614' ORDER BY T1.ASSY_PLAN_DATE DESC; order by有问题
10-28
你提供的 SQL 查询中，`ORDER BY` 子句放在 `UNION ALL` 之后，是合法的，但当前写法存在问题： ```sql ORDER BY T1.ASSY_PLAN_DATE DESC; ``` ### ❌ 问题原因： - 在 `UNION ALL` 查询中，`ORDER BY` 只能引用最终结果集的列名，而不能引用来自某个子查询的别名（如 `T1.ASSY_PLAN_DATE`）。 - 因为 `UNION ALL` 后的两个查询结果合并成一个结果集，此时 `T1` 这个别名已经不存在了，数据库无法识别 `T1.ASSY_PLAN_DATE`。 --- ### ✅ 正确写法： 你需要使用列的别名（即 `SELECT` 中定义的 `AS` 名称）或列的序号来排序。 #### ✅ 方法一：使用列别名排序（推荐） ```sql ORDER BY ASSY_PLAN_DATE DESC ``` #### ✅ 方法二：使用列序号排序（不推荐，维护性差） ```sql ORDER BY 12 DESC -- 假设 ASSY_PLAN_DATE 是第12个字段 ``` --- ### ✅ 修改后的完整 SQL 示例： ```sql ( SELECT COALESCE(T8.PROJECT_NO, T1.PROJECT_NO) AS PROJECT_NO, COALESCE(T8.PIPE_NO, T1.PIPE_NO) AS PIPE_NO, COALESCE(T8.PIPE_VERSION, T1.PIPE_VERSION) AS PIPE_VERSION, COALESCE(T8.IS_TOP_VERSION, T3.IS_TOP_VERSION) AS IS_TOP_VERSION, COALESCE(T8.IS_DELETE, T3.IS_DELETE) AS IS_DELETE, COALESCE(T8.IS_PAUSE, T3.IS_PAUSE) AS IS_PAUSE, T3.WEIGHT, T3.INCH, T4.WORK_SPACE_NO AS cutPlanWorkSpaceNo, T5.WORK_SPACE_NO AS assyPlanWorkSpaceNo, T6.WORK_SPACE_NO AS weldingPlanWorkSpaceNo, COALESCE(T8.CUT_PLAN_DATE, T1.CUT_PLAN_DATE) AS CUT_PLAN_DATE, COALESCE(T8.ASSY_PLAN_DATE, T1.ASSY_PLAN_DATE) AS ASSY_PLAN_DATE, COALESCE(T8.WELDING_PLAN_DATE, T1.WELDING_PLAN_DATE) AS WELDING_PLAN_DATE, COALESCE(T8.WELDING_PRE_INSP_PLAN_DATE, T1.WELDING_PRE_INSP_PLAN_DATE) AS WELDING_PRE_INSP_PLAN_DATE, COALESCE(T8.WELDING_POST_INSP_PLAN_DATE, T1.WELDING_POST_INSP_PLAN_DATE) AS WELDING_POST_INSP_PLAN_DATE, COALESCE(T8.IN_BASKET_PLAN_DATE, T1.IN_BASKET_PLAN_DATE) AS IN_BASKET_PLAN_DATE, T7.INST_NEED_DATE, T7.CRAFT_LINE_TYPE, (COALESCE(T8.IN_BASKET_PLAN_DATE, T1.IN_BASKET_PLAN_DATE) - COALESCE(T8.CUT_PLAN_DATE, T1.CUT_PLAN_DATE)) AS PIPE_PRE_CYC FROM CP_PIPE_PLAN_DESP T1 LEFT JOIN CP_PIPE_PLAN T2 ON T1.PLAN_NO = T2.PLAN_NO AND T1.PLAN_VERSION = T2.PLAN_VERSION AND T1.PROJECT_NO = T2.PROJECT_NO AND T2.PLAN_TYPE = '预制' LEFT JOIN CP_PIPE_DESIGN_INFO T3 ON T1.PROJECT_NO = T3.PROJECT_NO AND T1.PIPE_NO = T3.PIPE_NO AND T1.PIPE_VERSION = T3.PIPE_VERSION LEFT JOIN CP_PIPE_PROD_INFO T7 ON T3.PROJECT_NO = T7.PROJECT_NO AND T3.PIPE_NO = T7.PIPE_NO AND T3.PIPE_VERSION = T7.PIPE_VERSION LEFT JOIN CP_WORK_SPACE T4 ON T1.CUT_WORK_SPACE_ID = T4.ID LEFT JOIN CP_WORK_SPACE T5 ON T1.ASSY_WORK_SPACE_ID = T5.ID LEFT JOIN CP_WORK_SPACE T6 ON T1.WELDING_WORK_SPACE_ID = T6.ID LEFT JOIN CP_PIPE_PLAN_ADD_ITEM_EDIT_TEMP T8 ON T1.PLAN_NO = T8.PLAN_NO AND T1.PLAN_VERSION = T8.PLAN_VERSION AND T1.PROJECT_NO = T8.PROJECT_NO AND T1.PIPE_NO = T8.PIPE_NO AND T1.PIPE_VERSION = T8.PIPE_VERSION WHERE T1.PLAN_NO = 'YPH614202511' AND T1.PLAN_VERSION = 6 AND T1.PROJECT_NO = 'H614' AND T2.ORG_NO = 'C000030' ) UNION ALL ( SELECT T1.PROJECT_NO, T1.PIPE_NO, T1.PIPE_VERSION, T1.IS_TOP_VERSION, T1.IS_DELETE, T1.IS_PAUSE, T3.WEIGHT, T3.INCH, T4.WORK_SPACE_NO AS cutPlanWorkSpaceNo, T5.WORK_SPACE_NO AS assyPlanWorkSpaceNo, T6.WORK_SPACE_NO AS weldingPlanWorkSpaceNo, T1.CUT_PLAN_DATE, T1.ASSY_PLAN_DATE, T1.WELDING_PLAN_DATE, T1.WELDING_PRE_INSP_PLAN_DATE, T1.WELDING_POST_INSP_PLAN_DATE, T1.IN_BASKET_PLAN_DATE, T7.INST_NEED_DATE AS needDate, T7.CRAFT_LINE_TYPE, (T1.IN_BASKET_PLAN_DATE - T1.CUT_PLAN_DATE) AS PIPE_PRE_CYC FROM CP_PIPE_PLAN_ADD_ITEM_EDIT_TEMP T1 LEFT JOIN CP_PIPE_PLAN T2 ON T1.PLAN_NO = T2.PLAN_NO AND T1.PLAN_VERSION = T2.PLAN_VERSION AND T1.PROJECT_NO = T2.PROJECT_NO AND T2.PLAN_TYPE = '预制' LEFT JOIN CP_PIPE_DESIGN_INFO T3 ON T1.PROJECT_NO = T3.PROJECT_NO AND T1.PIPE_NO = T3.PIPE_NO AND T1.PIPE_VERSION = T3.PIPE_VERSION LEFT JOIN CP_PIPE_PROD_INFO T7 ON T3.PROJECT_NO = T7.PROJECT_NO AND T3.PIPE_NO = T7.PIPE_NO AND T3.PIPE_VERSION = T7.PIPE_VERSION LEFT JOIN CP_WORK_SPACE T4 ON T1.CUT_WORK_SPACE_ID = T4.ID LEFT JOIN CP_WORK_SPACE T5 ON T1.ASSY_WORK_SPACE_ID = T5.ID LEFT JOIN CP_WORK_SPACE T6 ON T1.WELDING_WORK_SPACE_ID = T6.ID WHERE NOT EXISTS ( SELECT 1 FROM CP_PIPE_PLAN_DESP T1 WHERE T1.PLAN_NO = T1.PLAN_NO AND T1.PLAN_VERSION = T1.PLAN_VERSION AND T1.PROJECT_NO = T1.PROJECT_NO AND T1.PIPE_NO = T1.PIPE_NO AND T1.PIPE_VERSION = T1.PIPE_VERSION ) AND T1.PLAN_NO = 'YPH614202511' AND T1.PLAN_VERSION = 6 AND T1.PROJECT_NO = 'H614' ) ORDER BY ASSY_PLAN_DATE DESC; ``` --- ### ✅ 总结： | 问题 | 解决方案 | |------|----------| | `ORDER BY T1.ASSY_PLAN_DATE` 报错 | 改为 `ORDER BY ASSY_PLAN_DATE` | | `UNION ALL` 后排序问题 | 使用列别名或列序号排序 | ---
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值