加入收藏 | 设为首页 | 会员中心 | 我要投稿 李大同 (https://www.lidatong.com.cn/)- 科技、建站、经验、云计算、5G、大数据,站长网!
当前位置: 首页 > 编程开发 > Java > 正文

在多线程并发设置中使用unixODBC

发布时间:2020-12-14 23:49:48 所属栏目:Java 来源:网络整理
导读:我要问并回答这个问题,因为我花了很长时间才弄明白,我希望答案一直在这里开始. 问题:一个长时间运行的unixODBC查询阻止来自同一个应用程序的所有其他查询. 问题是:如何阻止这种情况发生. 解决方法 答案,以__handles.c的剪切和粘贴评论的形式 – 我知道,为
我要问并回答这个问题,因为我花了很长时间才弄明白,我希望答案一直在这里开始.

问题:一个长时间运行的unixODBC查询阻止来自同一个应用程序的所有其他查询.

问题是:如何阻止这种情况发生.

解决方法

答案,以__handles.c的剪切和粘贴评论的形式 – 我知道,为什么不是每个人都想在那里寻找文档,对吧?
/*
 * use just one mutex for all the lists,this avoids any issues
 * with deadlocks,the performance issue should be minimal,if it
 * turns out to be a problem,we can readdress this
 *
 * We also have a mutex to protect the connection pooling code
 *
 * If compiled with thread support the DM allows four different
 * thread strategies
 *
 * Level 0 - Only the DM internal structures are protected
 * the driver is assumed to take care of it's self
 *
 * Level 1 - The driver is protected down to the statement level
 * each statement will be protected,and the same for the connect
 * level for connect functions,note that descriptors are considered
 * equal to statements when it comes to thread protection.
 *
 * Level 2 - The driver is protected at the connection level. only
 * one thread can be in a particular driver at one time
 *
 * Level 3 - The driver is protected at the env level,only one thing
 * at a time.
 *
 * By default the driver open connections with a lock level of 3,* this can be changed by adding the line
 *
 * Threading = N
 *
 * to the driver entry in odbcinst.ini,where N is the locking level
 * (0-3)
 *
 */

(编辑:李大同)

【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!

    推荐文章
      热点阅读