blocks|key|1170199|text|您需要增加连接的超时时间。如果你因为某些原因不能或不想这样做，你可以试着调用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1170200|data+=+db.query(sql).store_result()|code-block|syntax|javascript|1170201|这将立即获取所有结果，这样您的连接就不会在迭代它们的过程中超时。|1170202|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You need to increase the timeout on your connection. If you can't or don't want to do that for some reason, you could try calling:

<pre><code>data = db.query(sql).store_result()
</code></pre>

This will fetch all the results immediately, then your connection won't time out halfway through iterating over them.

blocks|key|1170249|text|确保在连接前关闭游标。我已经解决了我的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1170250|if+cur+and+con:++++++++++++++++++++++++
++++cur.close()+
++++con.close()+|code-block|syntax|javascript|1170251|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Make sure you close cursor before connection. I've resolved my problem with this:

<pre><code>if cur and con: 
 cur.close() 
 con.close() 
</code></pre>

blocks|key|1385526|text|将“max_allowed_packet”设置为64M，然后重新启动MySql服务器。如果这不能解决您的问题，那么问题可能出在其他地方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1385527|我有一个执行同时查询的多线程PHP+CLI应用程序，最近我注意到了这个问题。对我来说，现在很明显，MySql服务器将来自同一IP的所有连接都视为一个“单一”连接，因此只要一个查询完成，就会丢弃所有连接。|1385528|我想知道，有没有办法让MySql允许来自同一个IP的100个连接，并将每个连接视为一个单独的连接。|1385529|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Set the 'max_allowed_packet' setting to 64M and restart your MySql server. If that did not fixed your issues, the problem may lie elsewhere.

I've a multi-threaded PHP CLI application that does simultaneous queries and I recently noticed this issue. It's now obvious to me that MySql server consider all connections from the same IP as a 'single' connection and therefore drop all connections whenever a single query finishes.

I wonder though that is there a way to make MySql allow say 100 connections from the same IP and consider each connection as an individual connection.

blocks|key|1170442|text|这发生在我的mariadb上，因为我把一个varchar(255)专栏变成了一个unique+key。我猜这对于唯一的来说太重了，因为插入超时了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1170443|entityMap^0|L|C|14|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

This was happening to me with mariadb because I made a <code>varchar(255)</code> column a <code>unique key</code>.. guess that's too heavy for a unique, as the insert was timing out.

blocks|key|1170605|text|如果有人或某事使用KILL+command切断了您的连接，也会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1170606|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.5/en/kill.html^0|9|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This can also happen if someone or something kills your connection using the <a href="http://dev.mysql.com/doc/refman/5.5/en/kill.html" rel="nofollow">KILL command</a>.

blocks|key|1385843|text|当我试图更新一个磁盘上的大小大于可用磁盘空间的表时，就会发生这种情况。对我来说，解决方案就是增加可用的磁盘空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1385844|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This happened to me when I tried to update a table whose size on disk was bigger than the available disk space. The solution for me was simply to increase the available disk space.

blocks|key|1170685|text|在我的例子中，我在寻找SQL转储时遇到了这个问题，该转储以错误的顺序放置了表。有问题的创建包含一个约束...引用了尚未创建的表的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1170686|我找到了有问题的表，并将其CREATE语句移到了有问题的表的上方，错误消失了。|1170687|我遇到的与这个错误转储相关的另一个错误是错误1005/+errno:+150+--+"Can't+create+table“，同样是表创建顺序混乱的问题。|1170688|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, I ran into this problem when sourcing an SQL dump which had placed the tables in the wrong order. The CREATE in question included a CONSTRAINT ... REFERENCES that referenced a table that had not been created yet.

I located the table in question, and moved its CREATE statement to above the offending one, and the error disappeared.

The other error I encountered relating to this faulty dump was ERROR 1005/ errno: 150 -- "Can't create table" , again a matter of tables being created out of order.

blocks|key|1385985|text|当我的CONSTRAINT名称与其他CONSTRAINT名称同名时，我就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1385986|更改我的CONSTRAINT名称解决了这个问题。|1385987|entityMap^0|3|A|I|A|0|4|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

This happend to me when my <code>CONSTRAINT</code> name have the same name with other <code>CONSTRAINT</code> name.

Changing my <code>CONSTRAINT</code> name solved this.

blocks|key|1170781|text|我也遇到过类似的问题。在我的例子中，它是通过以这种方式获取光标来解决的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1170782|cursor+=+self.conn.cursor(buffered=True)|code-block|syntax|javascript|1170783|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I encountered similar problems too. In my case it was solved by getting the cursor in this way:

<pre><code>cursor = self.conn.cursor(buffered=True)
</code></pre>

blocks|key|1386115|text|多处理和Django+DB不能很好地结合在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1386116|在新的过程中，我最终关闭了Django+DB连接。|1386117|这样就不会引用父级所使用的连接。|1386118|from+multiprocessing+import+Pool

multi_core_arg+=+[[1,2,3],+[4,5,6],+[7,8,9]]
n_cpu+=+4
pool+=+Pool(n_cpu)
pool.map(_etl_,+multi_core_arg)
pool.close()
pool.join()

def+_etl_(x):
++++from+django.db+import+connection+
++++connection.close()+
++++print(x)|code-block|syntax|javascript|1386119|或|1386120|Process.start()调用以以下开头的函数|offset|length|style|CODE|1386121|其他一些建议使用|1386122|from+multiprocessing.dummy+import+Pool+as+ThreadPool|1386123|它解决了我的(2013，丢失连接)问题，但线程在执行IO时使用GIL，以便在IO结束时释放它。|1386124|相比之下，进程会产生一组相互通信的工作进程，这可能会更慢。|1386125|我建议你给它计时。另外一个小贴士是使用由scikit+learn项目支持的joblib。一些性能结果表明，它的性能优于本机Pool()。尽管它将验证真实的运行时间开销的责任留给了程序员。|1386126|entityMap|0|LINK|mutability|MUTABLE|url|http://pythonhosted.org/joblib/parallel.html^0|0|0|0|0|0|0|F|0|0|0|0|0|11|6|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1D|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@$O|1G|P|1H|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|1J|8|@]|9|@]|A|$I|J]]|$1|W|3|X|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1M|8|@]|9|@$O|1N|P|1O|1|1P]]|A|$]]|$1|12|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Multiprocessing and Django DB don't play well together. 

I ended up closing Django DB connection first thing in the new process. 

So that one will have no references to the connection used by the parent. 

<pre><code>from multiprocessing import Pool

multi_core_arg = [[1,2,3], [4,5,6], [7,8,9]]
n_cpu = 4
pool = Pool(n_cpu)
pool.map(_etl_, multi_core_arg)
pool.close()
pool.join()

def _etl_(x):
 from django.db import connection 
 connection.close() 
 print(x)
</code></pre>

OR

<code>Process.start()</code> calls a function which starts with

Some other suggest to use 

<pre><code>from multiprocessing.dummy import Pool as ThreadPool
</code></pre>

It solved my (2013, Lost connection) problem, but thread use GIL, when doing IO, to will release it when IO finish.

Comparatively, Process spawn a group of workers that communication each other, which may be slower.

I recommend you to time it.
A side tips is to use <a href="http://pythonhosted.org/joblib/parallel.html" rel="nofollow noreferrer">joblib</a> which is backed by scikit-learn project.
some performance result shows it out perform the native Pool().. although it leave the responsibility to coder to verify the true run time cost.

blocks|key|1386209|text|我也遇到了同样的问题。由于其他一些问题，我曾尝试将cnx.close()行添加到其他函数中。相反，我删除了所有这些无关的闭包，并像这样设置我的类：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1386210|class+DBase:

config+=+{
++++++'user':+'root',
++++++'password':+'',
++++++'host':+'127.0.0.1',
++++++'database':+'bio',
++++++'raise_on_warnings':+True,
++++++'use_pure':+False,
++++++}

def+__init__(self):
++++import+mysql.connector
++++self.cnx+=+mysql.connector.connect(**self.config)
++++self.cur+=+self.cnx.cursor(buffered=True)
++++print(self.cnx)
def+__enter__(self):
++++return+DBase()

def+__exit__(self,+exc_type,+exc_val,+exc_tb):
++++self.cnx.commit()
++++if+self.cnx:
++++++++self.cnx.close()|code-block|syntax|javascript|1386211|在这个类中调用的任何函数都是connects、commits和closes。|1386212|entityMap^0|P|B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

I was running into the same problem. Because of some other issues I had tried to add a <code>cnx.close()</code> line to my other functions. Instead, I removed all these extraneous closes and setup my class like this:

<pre><code>class DBase:

config = {
 'user': 'root',
 'password': '',
 'host': '127.0.0.1',
 'database': 'bio',
 'raise_on_warnings': True,
 'use_pure': False,
 }

def __init__(self):
 import mysql.connector
 self.cnx = mysql.connector.connect(**self.config)
 self.cur = self.cnx.cursor(buffered=True)
 print(self.cnx)
def __enter__(self):
 return DBase()

def __exit__(self, exc_type, exc_val, exc_tb):
 self.cnx.commit()
 if self.cnx:
 self.cnx.close()
</code></pre>

Any function that is called within this class is connects, commits, and closes.

blocks|key|1386315|text|非常简单的解决方法是，转到phpadmin的控制面板，单击config/，然后编辑您看到的.ini文件。查找端口3306，如果该端口不是用于连接的端口，请将3306更改为您正在使用的端口。在您的登录屏幕上，只需输入您的服务器的本地主机，您的端口，如果它不是默认的，或者如果您没有在sql配置中更改文件名my.ini，请将其保留为原样。然后输入用户名:root或您创建的用户名，然后输入密码:1234或您分配的密码。如果是本地连接，请不要选中url选项。然后键入要编辑的数据库的名称。注意:连接后，您将看到您的服务器或要连接到的服务器上的数据库列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1386316|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

very simple to solve, go to the control panel of you phpadmin and click on config/then edit the .ini file you see. look for port 3306 if that's not the port you are using for your connection change 3306 to the port you are using. on your login screen just put localhost for your server, your port if its not the default or if you did not change the file name my.ini in sql configuration leavit as is. then put your username:root or the one you created then the password:1234 or the one you assigned. if you are connecting localy, do not check the url option. then type the name of the database you want to edit. note: once you are connected you will see the list of databases you have on your server or the server you are connecting to.

blocks|key|1386377|text|当我试图对数百万条记录进行批量插入时，我遇到了这个错误，出现了“管道破裂”。我最终解决了这个问题，方法是将数据分成较小的批处理大小，然后使用mysql游标为我需要执行的每个插入操作运行一个executemany命令。这解决了问题，似乎没有以任何明显的方式影响性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1386378|例如：|1386379|def+chunks(data):
++++for+i+in+range(0,+len(data),+CHUNK_SIZE):
++++++++yield+data[i:i+%2B+CHUNK_SIZE]


def+bulk_import(update_list):
++++new_list+=+list(chunks(update_list))
++++for+batch+in+new_list:
+++++++++cursor.execute(#SQL+STATEMENT+HERE)|code-block|syntax|javascript|1386380|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was getting this error with a "broken pipe" when I tried to do bulk inserts with millions of records. I ended up solving this by chunking my data into smaller batch sizes and then running an executemany command with the mysql cursor for each of the inserts I needed to do. This solved the problem and didn't seem to affect the performance in any noticeable way. 

eg. 

<pre><code>def chunks(data):
 for i in range(0, len(data), CHUNK_SIZE):
 yield data[i:i + CHUNK_SIZE]


def bulk_import(update_list):
 new_list = list(chunks(update_list))
 for batch in new_list:
 cursor.execute(#SQL STATEMENT HERE)
</code></pre>

blocks|key|1386438|text|与@imxylz相同，但我必须使用mycursor.execute('set+GLOBAL+max_allowed_packet=67108864')，因为我在没有使用全局参数的情况下得到了一个只读错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1386439|mysql.connector.__version__+|code-block|syntax|javascript|1386440|8.0.16|1386441|entityMap^0|H|1M|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

The same as @imxylz, but I had to use <code>mycursor.execute('set GLOBAL max_allowed_packet=67108864')</code> as I got a read-only error without using the GLOBAL parameter.

<pre><code>mysql.connector.__version__ 
</code></pre>

8.0.16

blocks|key|1171221|text|在使用mariadb，sqlalchemy和pandas时，同样的情况也发生在我身上，就像上面的@iamapotatoe一样，我也创建了一个函数，将数据帧分成块，并将它们一点一点地移植到sql数据库中。特别是在mysql配置选项中更改max_allowed_packet对您无效的情况下，可以利用这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1171222|def+load_large_df(table_name,df_to_load,batch_size,engine):
++++df_to_load+=+df_to_load.dropna(how='all')
++++with+engine.connect()+as+conn:
++++++++conn.execute(f"DROP+TABLE+IF+EXISTS+{table_name}")
++++++++rows+=+df_to_load.shape[0]
++++++++batch+=+int(rows/batch_size)
++++++++

++++++++strt+=+0
++++++++while+strt+<+rows:
++++++++++++df+=+df_to_load[strt:].head(batch)
++++++++++++df.to_sql(table_name,con=conn,if_exists='append')
++++++++++++strt+%2B=+batch|code-block|syntax|javascript|1171223|entityMap^0|3|7|B|A|M|6|1C|C|39|I|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|L|$]]

This very same situation happened to me while working with <code>mariadb </code>, <code>sqlalchemy</code> and <code>pandas</code> and just like <code>@iamapotatoe</code> above I also created a function to break up the dataframe into chunks and port them over to the sql database bit by bit.
This can be utilized especially if changing the <code>max_allowed_packet</code> in the mysql config option doesn't work for you .
<pre><code>def load_large_df(table_name,df_to_load,batch_size,engine):
 df_to_load = df_to_load.dropna(how='all')
 with engine.connect() as conn:
 conn.execute(f&quot;DROP TABLE IF EXISTS {table_name}&quot;)
 rows = df_to_load.shape[0]
 batch = int(rows/batch_size)
 

 strt = 0
 while strt &lt; rows:
 df = df_to_load[strt:].head(batch)
 df.to_sql(table_name,con=conn,if_exists='append')
 strt += batch
</code></pre>

blocks|key|1386575|text|你可以看到我对类似问题的回答：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1386576|https://stackoverflow.com/a/69610550/16647254|offset|length|1386577|使用锁来解决此问题|1386578|lock.acquire()
mysqlhelper.getconn()
result_db_num+=+mysqlhelper.update(sql,+[businessid,+md5_id])
mysqlhelper.end()
mysqlhelper.dispose()
lock.release()|code-block|syntax|javascript|1386579|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|19|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|C]]]]

You can see my answer followed for similar problem:
<a href="https://stackoverflow.com/a/69610550/16647254">https://stackoverflow.com/a/69610550/16647254</a>
use lock to solve this problem
<pre><code>lock.acquire()
mysqlhelper.getconn()
result_db_num = mysqlhelper.update(sql, [businessid, md5_id])
mysqlhelper.end()
mysqlhelper.dispose()
lock.release()
</code></pre>

I have a huge table and I need to process all rows in it. I'm always getting this Lost connection message and I'm not able to reconnect and restore the cursor to the last position it was. This is basically the code I have here:

<pre><code>#
import MySQLdb

class DB:
 conn = None

 def connect(self):
 self.conn = MySQLdb.connect('hostname', 'user', '*****', 'some_table', cursorclass=MySQLdb.cursors.SSCursor)

 def query(self, sql):
 try:
 cursor = self.conn.cursor()
 cursor.execute(sql)
 except (AttributeError, MySQLdb.OperationalError):
 self.connect()
 cursor = self.conn.cursor()
 cursor.execute(sql)
 return cursor
#

#
db = DB()
sql = "SELECT bla FROM foo"
data = db.query(sql)

for row in data:
 do_something(row)
#
</code></pre>

But I'm always getting this:

<pre><code>#
Traceback (most recent call last):
 File "teste.py", line 124, in &lt;module&gt;
 run()
 File "teste.py", line 109, in run
 for row in data:
 File "/usr/lib64/python2.5/site-packages/MySQLdb/cursors.py", line 417, in next
 row = self.fetchone()
 File "/usr/lib64/python2.5/site-packages/MySQLdb/cursors.py", line 388, in fetchone
 r = self._fetch_row(1)
 File "/usr/lib64/python2.5/site-packages/MySQLdb/cursors.py", line 285, in _fetch_row
 return self._result.fetch_row(size, self._fetch_type)
 _mysql_exceptions.OperationalError: (2013, 'Lost connection to MySQL server during query')
 Exception _mysql_exceptions.OperationalError: (2013, 'Lost connection to MySQL server during query') in &lt;bound method SSCursor.__del__ of &lt;MySQLdb.cursors.SSCursor object at 0x7f7e3c8da410&gt;&gt; ignored
#
</code></pre>

Do you have any idea?

Lost connection to MySQL server during query

数据库

服务器

Django

MySQL

我有一个很大的表，需要处理其中的所有行。我总是收到丢失连接的消息，并且我无法重新连接并将光标恢复到上次的位置。这基本上就是我这里的代码：#import MySQLdbclass DB:  conn = None  def connect(self):    self.conn = MySQLdb.connect('ho...

问查询过程中失去与MySQL服务器的连接
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查询过程中失去与MySQL服务器的连接EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查询过程中失去与MySQL服务器的连接
EN