最近在做的项目中有用到pymysql线程池的使用,并且是在多线程场景下使用,使用过程中实际跑多线程遇到了一些错误,所以借此机会简单分析了一下。
先看一下下面的代码多线程场景下跑是否会有问题?
dao/dbcon.py
# -*-coding:utf-8-*-
import pymysql
from DBUtils.PooledDB import PooledDB
from conf.config import ConfParser
from logger.logger import *
conf = ConfParser()
class DB(object):
"""docstring for DbConnection"""
__pool = None
def __init__(self):
self.pool = DB.__get_conn()
self.conn = None
self.cursor = None
@staticmethod
def __get_conn():
if DB.__pool is None:
try:
DB.__pool = PooledDB(creator=pymysql, host=conf.get("DB", "host"), port=int(conf.get("DB", "port")), user=conf.get("DB", "user"), passwd=conf.get("DB", "passwd"), db=conf.get("DB", "db"), charset=conf.get("DB", "charset"))
except Exception as e:
logging.error("%s : %s" % (Exception, e))
return DB.__pool
def connect(self, cursor=pymysql.cursors.DictCursor):
self.conn = self.pool.connection()
self.cursor = self.conn.cursor(cursor=cursor)
return self.cursor
def close(self):
self.cursor.close()
self.conn.close()
def query_sql(self, sql, params=None):
self.connect()
self.cursor.execute(sql, params)
result = self.cursor.fetchall()
self.close()
return result
def execute_sql(self, sql, params=None):
self.connect()
try:
self.cursor.execute(sql, params)
result = self.cursor.lastrowid
self.conn.commit()
self.close()
except Exception as e