AFX_ODBC_CALL(:: SQLExecute(m hstmt)花费的时间太长 [英] AFX_ODBC_CALL(::SQLExecute(m hstmt) takes too long

查看:61
本文介绍了AFX_ODBC_CALL(:: SQLExecute(m hstmt)花费的时间太长的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

AFX_ODBC_CALL(:: SQLExecute(m hstmt)花太长时间了???有时系统挂起.我想读取图像并将blob数据保存在CLongBinary变量中,然后我想将其保存在mysql的blob字段中

AFX_ODBC_CALL(::SQLExecute(m hstmt) takes too long??? Sometimes system hangs. I want to read the image and save the blob data in CLongBinary variable and then i want to save it in the blob field of the mysql database. While executing the open statement of the CRecordset, it takes almost 60% usage of CPU and sometimes it hangs the system. What is the problem behind this??

推荐答案

很难说的是有限的信息.
您是否尝试过连续两次运行查询并查看时间是否相同?可能是第一次调用需要加载MySQL,这可能需要一段时间,或者数据库很大,并且查询会导致严重的延迟.您需要先确定瓶颈在哪里,然后才能开始进行治愈.
Difficult to say with that limited an information.
Have you tried running the query twice in succession and seeing if the timing is the same? It may be that the first call needs to load MySQL, which can take a while, or the database is huge and your query causes a major delay. You need to look at identifying where your bottle neck is before you can start to cure it.


这篇关于AFX_ODBC_CALL(:: SQLExecute(m hstmt)花费的时间太长的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆