Quantcast
Channel: MySQL Forums - Connector/Python

create database and user via a python script ran as sudo (no replies)

0
0
Hello
I am writing a python script which I runas sudo. The goal of the python script is to create a user and a database for this user.
I get the following message.
>>> mydb = mysql.connector.connect( host = "localhost", user = user, password = "mypassword")
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/mysql/connector/connection_cext.py", line 236, in _open_connection
self._cmysql.connect(**cnx_kwargs)
_mysql_connector.MySQLInterfaceError: Access denied for user 'root'@'localhost'

This happens just after the installation of the package mysql server. Thus I have not yet granted any privileges to root.

Is this the cause of the problem? should I write a shell script to install all my sql packages and grant the privileges??
I thank you for your help.

MySQL 8.0.29: Release Notes (no replies)

0
0

script crashes on last day of month but works every other day (3 replies)

0
0
Hi
I have this python script using mysql.connector
I am using a raspberry pi 4 and the db is MariaDB version 10.5.15

I hope this the right forum to ask this question so here goes.

#!/usr/bin/python3

### imports ###
import mysql.connector
import datetime
import schedule
import time

### connect to mysql ###

def check_date():
db = mysql.connector.connect(
host="localhost",
user="user",
password="hello",
database="there"
)

print("connect")

cursor = db.cursor()
sql = "(select count(*) from meter where date = current_date() + 1)"
cursor.execute(sql)
result = cursor.fetchone()
cursor.close()
today = result[0]
print("check")
print(today)
if today == 1:
db.close()
print("------------")
return

else:
mycursor = db.cursor()
sql = "insert into meter (date, water_in_lts, rain_gauge) Values (%s, %s, %s)"
val = (datetime.datetime.now() + datetime.timedelta(days=1), 0, 0)
mycursor.execute(sql, val)
db.commit()
print("insert")
check_date()

check_date()

schedule.every().day.at("00:01").do(check_date)
#schedule.every().minutes.do(check_date)

while True:
schedule.run_pending()
time.sleep(1)


Its purpose is to insert tomorrows date into my database so other scrips can then update other fields for the current day

This works fine on every day except the last day of the month in which it just crashes and burns.

looking at the logs it seems that it a MYSQL problem rather than python
the logs say that I have a duplicate entry for the date column

The script runs as a service and spends all of the last day of the month crashing but as soon as the date turn to the first of the next month it runs fine.

can any one see why this would happen?


Regards Neil

Bad magic number (1 reply)

0
0
Hi, This is Rohan from F60 Host
I installed a mysql database with the python connector but when I'm trying to test if the connector works with "import mysql.connector" I'm getting the following error: ImportError: bad magic number in 'mysql': b'T\r\r\n'
https://f60host.com/

Bad magic number (no replies)

0
0
Hi, This is Dhaval from Ananka Fasteners
I installed a mysql database with the python connector but when I'm trying to test if the connector works with "import mysql.connector" I'm getting the following error: ImportError: bad magic number in 'mysql': b'T\r\r\n'

Unable to log to a file executing infinite loops while polling data from python-telegram-bot (no replies)

0
0
I'm NOT a programmer, but a very enthusiast user :) I've implemented a logger with influxdb, grafana and a connection to a modbus interface via tcp/ip with python. All works well, but i have a big issue, i cannot have LOGS of the activities, maybe for the bad construct i've used. Basically i should have the bot listening, and another infinite thread who pull data from an inverter. Here is a cutted version of the construct i've used:

def start(update: Updater, context: CallbackContext):
update.message.reply_text('Whatever command/action/function i want')

def anothercommand(update: Updater, context: CallbackContext):
update.message.reply_text('Whatever command/action/function i want')

def loop(update: Updater, context: CallbackContext):
print('Starting thread for automations')
def thread1(update: Updater, context: CallbackContext):
while 1:
#loop to collect data into dB and send automated TG Alerts
update.message.reply_text('I am from thread 1. going to sleep now.')
time.sleep(2)
t1 = threading.Thread(target=thread1,args=(update,context))
t1.start()

def main() -> None:
print('bot started..')
updater = Updater(TOKEN,use_context=True)
dispatcher = updater.dispatcher
loop(updater,CallbackContext)
dispatcher.add_handler(CommandHandler('start', start))
dispatcher.add_handler(CommandHandler('anothercommand', anothercommand))
updater.start_polling()
updater.idle()

if __name__ == '__main__':
main()
...forcing the logging to a file :

sys.stdout = open('/the/path/to/your/file', 'w')
or with

file.py > output.txt
or

import logging
logging.basicConfig(filename='example.log', encoding='utf-8', level=logging.DEBUG)
generate an empty logfile, and nothing appears on the console

Python VBA DRIVER={MySQL ODBC 5.1 Driver (no replies)

0
0
Hello,

I received an Excel VBA Code which takes data from MySQL to VBA.
I would like to take the same MySQL data to my python.

I struggle addressing the MYSQl with my Python.

String in VBA:

DRIVER={MySQL ODBC 5.1 Driver};Port=3308;DATABASE=pbh;UID=user;PWD=password#


thanks

protobuf requires Python '>=3.7' but the running Python is 3.6.8 (2 replies)

0
0
Hi,
I'm trying to install mysql-connector-python on Centos7 which has Python 3.6.8 installed.

pip3 install mysql-connector-python

results with:
protobuf requires Python '>=3.7' but the running Python is 3.6.8

How to overcome that issue?

Thanks much, OE

Cannot commit a read statement (3 replies)

0
0
```
>>> import mysql.connector
>>> cnx = mysql.connector.connect(user="root")
>>> cur = cnx.cursor()
>>> cur.execute('select count(*) from test.test')
>>> cnx.commit()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/opt/homebrew/lib/python3.9/site-packages/mysql/connector/connection.py", line 1229, in commit
self._execute_query("COMMIT")
File "/opt/homebrew/lib/python3.9/site-packages/mysql/connector/connection.py", line 1247, in _execute_query
self.handle_unread_result()
File "/opt/homebrew/lib/python3.9/site-packages/mysql/connector/connection.py", line 1455, in handle_unread_result
raise errors.InternalError("Unread result found")
mysql.connector.errors.InternalError: Unread result found
```

commit a select statement always return a "Unread result found" error. Is this expected? Same code works well with mysqlclient and PyMySQL.

MySQL 8.0.30: Release Notes (no replies)

0
0

pooled connection trauma (6 replies)

0
0
I hit an issue caused by the need to move to connection pools.
I was initially using Connector/Python 8.0.21 with mySQL server 5.6.10 however discovered that an exception would be thrown if I created the pool with pool_reset_session=True, when closing the connection, mysql.connector.errors.NotSupportedError: MySQL version 5.7.2 and earlier does not support COM_RESET_CONNECTION.
I was surprised by this as release notes say that this issue was fixed in Connector/Python 8.0.16

In moving to Connector/Python 8.0.29 the exception thrown, mentioned above, was fixed.
However I then found that my stored procedures would cause the following exception: mysql.connector.errors.ProgrammingError: 1064 (42000): You have an error in your SQL syntax

Currently the only way around this replacement of stored procedures with normal queries.

Any thoughts on what I have described appreciated.

'Not naive datetime (tzinfo is already set)') (no replies)

0
0
Hi Guys,

Anyone seen this message in SQL operations?
(venv) root@84ff53e702e9:/www_root# python manage.py migrate
Traceback (most recent call last):
File "manage.py", line 24, in <module>
main()
File "manage.py", line 20, in main
execute_from_command_line(sys.argv)
File "/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
utility.execute()
File "/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/venv/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/venv/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
File "/venv/lib/python3.8/site-packages/django/core/management/base.py", line 89, in wrapped
res = handle_func(*args, **kwargs)
File "/venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 92, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 18, in __init__
self.loader = MigrationLoader(self.connection)
File "/venv/lib/python3.8/site-packages/django/db/migrations/loader.py", line 53, in __init__
self.build_graph()
File "/venv/lib/python3.8/site-packages/django/db/migrations/loader.py", line 220, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/venv/lib/python3.8/site-packages/django/db/migrations/recorder.py", line 78, in applied_migrations
return {(migration.app, migration.name): migration for migration in self.migration_qs}
File "/venv/lib/python3.8/site-packages/django/db/models/query.py", line 280, in __iter__
self._fetch_all()
File "/venv/lib/python3.8/site-packages/django/db/models/query.py", line 1324, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/venv/lib/python3.8/site-packages/django/db/models/query.py", line 68, in __iter__
for row in compiler.results_iter(results):
File "/venv/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1122, in apply_converters
value = converter(value, expression, connection)
File "/venv/lib/python3.8/site-packages/django/db/backends/mysql/operations.py", line 313, in convert_datetimefield_value
value = timezone.make_aware(value, self.connection.timezone)
File "/venv/lib/python3.8/site-packages/django/utils/timezone.py", line 242, in make_aware
return timezone.localize(value, is_dst=is_dst)
File "/venv/lib/python3.8/site-packages/pytz/__init__.py", line 245, in localize
raise ValueError('Not naive datetime (tzinfo is already set)')

Regards

python mysql client sample connection using kerberos (on windows) (no replies)

0
0
I'm having trouble finding any samples on connecting to a mysql db using the python client with sso (kerberos) from windows. Is there any chance documentation on this front can be added?

SSL routines:ssl_choose_client_version:unsupported protocol (no replies)

0
0
I have mysql-connector-python==8.0.29 installed on a windows desktop machine (python 3.7) connecting to an mysql server (mySQL server 5.6.10 on an EC2 instance) and connection pools are created and used just fine.

I then started to test the use of connection pools, on the target system, where the script that creates them runs (is the same as the windows machine above) but run on another AWS EC2 instance (Ubuntu 20.04.3 LTS (GNU/Linux 5.11.0-1022-aws x86_64)) and connects to the same mySQL server as above.

The AWS instance running the script is using mysql-connector-python==8.0.29 installed, however is running Python 3.8 not 3.7 (as with the windows machine). However I don't think the python version is causing the issue.

I get the following issue, which is potentially nothing to-do with mySQL and everything todo with SSL!

However I wondered if anyone had any recommendations/thoughts/wisdom?

-- Logs begin at Thu 2022-08-04 15:53:25 UTC. --
Aug 16 07:31:50 ip-address python3[126843]: return CMySQLConnection(*args, **kwargs)
Aug 16 07:31:50 ip-address python3[126843]: File "/usr/local/lib/python3.8/dist-packages/mysql/connector/connection_cext.py", line 94, in __init__
Aug 16 07:31:50 ip-address python3[126843]: self.connect(**kwargs)
Aug 16 07:31:50 ip-address python3[126843]: File "/usr/local/lib/python3.8/dist-packages/mysql/connector/abstracts.py", line 1052, in connect
Aug 16 07:31:50 ip-address python3[126843]: self._open_connection()
Aug 16 07:31:50 ip-address python3[126843]: File "/usr/local/lib/python3.8/dist-packages/mysql/connector/connection_cext.py", line 251, in _open_connection
Aug 16 07:31:50 ip-address python3[126843]: raise errors.get_mysql_exception(msg=exc.msg, errno=exc.errno,
Aug 16 07:31:50 ip-address python3[126843]: mysql.connector.errors.InterfaceError: 2026 (HY000): SSL connection error: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
Aug 16 07:31:50 ip-address systemd[1]: run_production_tests.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 07:31:50 ip-address systemd[1]: run_production_tests.service: Failed with result 'exit-code'.

Python mysql-connector doesn't handle numpy.nan (1 reply)

0
0
Hi,

My workflow requires that I bulk insert pandas dataframes to a mysql database.

pandas uses numpy.nan to represent null values in a dataframe's float columns.
Unfortunately, when converting said values to a query, the mysql-connector converts numpy.nan to a string; 'nan', failing to insert it to the float column in the db.

I have a code workaround where I replace all numpy.nan values with None, but that is compute intensive and takes up much more space.

Is it possible to open a pull request on mysql-connector github to fix this?

OverflowError: Python int too large to convert to C long (2 replies)

0
0
Hi,
Can someone help me with this problem?

The code below I ran on python 3.9.7 with mysql-connector-python 8.0.23 has no any problem.

#########################################################################
import mysqlx

ss = mysqlx.get_session({'host':'localhost', 'port':33060, 'user':'root', 'password':'xxxx'})
ss.drop_schema('testx')
ss.create_schema('testx')

db = ss.get_schema('testx')
db.create_collection('test')

col = db.get_collection('test')
col.add({'_id':'test', 'item':2147483648}).execute() # 8.0.23 pass, but 8.0.24 ~ 8.0.30 fail
#col.add({'_id':'test', 'item':2147483647}).execute() # this line is OK for any version

ss.drop_schema('testx')
ss.close()
#########################################################################

But, after I upgrading mysql-connector-python to 8.0.24 ~ 8.0.30(python version is 3.10.7),
it runs fail with the following error message.

-------------------------------------------------------------------------
OverflowError: Python int too large to convert to C long

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "R:\test.py", line 12, in <module>
col.add({'_id':'test', 'item':2147483648}).execute() # 8.0.23 pass, but 8.0.30 fail
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\statement.py", line 711, in execute
return self._connection.send_insert(self)
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\connection.py", line 494, in wrapper
result = func(self, *args, **kwargs)
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\connection.py", line 1150, in send_insert
self.protocol.send_msg(msg_type, msg)
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\protocol.py", line 835, in send_msg
self._writer.write_message(mysqlxpb_enum(msg_type), msg)
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\protocol.py", line 268, in write_message
msg_size = msg.byte_size(msg)
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\protobuf\__init__.py", line 541, in byte_size
else len(encode_to_bytes(msg.serialize_to_string()))
File "C:\Users\zmsun\AppData\Local\Programs\Python\Python310\lib\site-packages\mysqlx\protobuf\__init__.py", line 489, in serialize_to_string
return Protobuf.mysqlxpb.serialize_message(self._msg)
SystemError: <built-in function serialize_message> returned a result with an exception set
-------------------------------------------------------------------------

Is there anything I can change to fix this? Thanks.

Problem with inserting data into MySQL (no replies)

0
0
Hi
I want to read the data of a sensor and transfer it to MySQL local host with "mysql.connector". The problem is that it reads the data as a list containing 500 data (that is, it reads 500 to 500, not one by one). This is my code:

master_data = master_task.read(number_of_samples_per_channel=500)
sql = "INSERT INTO vib_data2 (data) VALUES (%s)"
val = list(master_data, )
mycursor.executemany(sql, val)
mydb.commit()


I got this error:
"Could not process parameters: float(-0.15846696725827258), it must be of type list, tuple or dict"


I can fix the problem with this code:

for i in master_data:
sql = "INSERT INTO vib_data2 (data) VALUES (%s)"
val = (str(I),)
mycursor.execute(sql, val)
mydb.commit()


But the code execution time is very long (more than one second) and thus some of the data is lost.
Thank you for helping to correct the code

I cannot implement python along with MySQL integration (2 replies)

0
0
I am facing issue that I can not implement MySQL in my system what would be main reason

mysql.connector.errors.InterfaceError: 2003 (2 replies)

Upgrade to a newer protobuf version (3 replies)

0
0
In Apache Airflow we have mysql-conneector-python integration that currently holds us back from upgrading to protobuf 4.

Having limitation to Requires-Dist: protobuf (<Requires-Dist: protobuf (<=3.20.3,>=3.11.0) prevents us from upgrading most of other providers - see apache/airflow#30067, Until mysql-connector-python fixes the dependency limitation, we will be forced to stop releasing the provider together with the others (it also means it will not be compatible with the other providers and newer versions of airflow when released

Can you please let us know if there are plans to upgrade the mysql-connector-python python sdk to not limit the protobuf? Otherwise we will have to exclude the mysql provider and stop releasing it.

Also see the devlist discussion thread I started about it (based on yandexcloud provider, but it applies to mysql too).

Thanks in advance!

Connection Arguments - host (2 replies)

0
0
Hi

How to configure host argument correctly when I have SQL DB on server instance?
I have configured user only for this instance.

When im trying put:
host='server_name\instance_name'
I have an error:
2005 (HY000): Unknown MySQL server host 'server_name\instance_name' (11001)

When im trying put only:
host='server_name'
I have only the information:
2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Regards
Mariusz

Support for protobufs 4? (3 replies)

0
0
The current latest version of mysql-connector-python (8.0.32) has a dependency conflict with the oldest version of google-ads (19.0.0) that works with current Google APIs (v12+).

The conflict is caused by:
google-ads 19.0.0 depends on protobuf>=4.21.5
mysql-connector-python 8.0.32 depends on protobuf<=3.20.3 and >=3.11.0


Are there plans to switch to protobuf 4.21.5+ under the covers?

Not all records - EOF deprecation / protocol.py (1 reply)

0
0
On larger queries - not all of the records are making it to my .fetchall() statement.

I've tracked it down to a potential issues within protocol.py, where a deprecated EOF is being detected, which stops reading in retrieved records.

I've had to comment out this section of code, and it seems to have solved my issue. Is this a bug, or a known incompatibility?

MySQL: /usr/sbin/mysqld (mysqld 5.7.41-0ubuntu0.18.04.1)
Python 3.9.5
MySQL Connector: mysql_connector-2.2.9-py3.9.egg-info

mysql/connector/protocol.py
Line 337-340
#elif eof57 and (packet[4] == 0 and packet[0] > 9):
# EOF deprecation: make sure we catch it whether flag is set or not
#eof = self.parse_ok(packet)
#rowdata = None

deallocating None issue with connect/disconnect (4 replies)

0
0
Hi all,

I run into a "deallocating None" error, if I use connect()/disconnect():
...
'None' refcount: 4
'None' refcount: 3
'None' refcount: 2
Fatal Python error: deallocating None
Python runtime state: initialized

Current thread 0x00007f9dfb640740 (most recent call first):
File "test.py", line 19 in <module>

Any ideas? Here my environment:
python: 3.8.10
OS: ubuntu 20.04
mysql-connector-python: 8.0.33

Samplecode to reproduce, just replace mysql.connector.connect() parameter with matching once:

import mysql.connector
from mysql.connector import Error
import sys
import time

if __name__ == "__main__":
while True:
try:
print(f"'None' refcount: {sys.getrefcount(None)}")
connection = mysql.connector.connect(
host = host,
port = port,
user = user,
passwd = password,
database = dbname
)
connection.disconnect()
time.sleep(0.01)
except Error:
print("error")
break

How to perform unit testing (4 replies)

0
0
I want to know how to execute unittests.py with my own database parameters.

Using mysql-connector-python 8.0.33 with MySQL 8.1 (2 replies)

0
0
Hi,

I would like to know if using mysql-connector-python 8.0.33 with MySQL 8.1 is officially supported, or if I am required to use mysql-connector-python==8.1.0.

Thanks for your help.

How to set a driver-side query execution timeout (no replies)

0
0
Hi, is there a way to set a driver-side query execution timeout? We noticed that the MySQL JDBC driver supports setting a driver-side socket/network timeout but the MySQL Python driver does not. This is a problem for us because if the server becomes unresponsive, any queries being executed will hang indefinitely. Is there a suggested solution for this problem?

SSL error using mysql-connector-python 8.2.0 (no replies)

0
0
Hello Experts,
i am using a simple python script to connect to mysql PAAS instance

import mysql.connector
from mysql.connector import errorcode
import os
try :
RPA_db = mysql.connector.connect(host="xxxx.mysql.database.azure.com", user="username",
database="rpa_log",password="YYYYYY",ssl_ca="C:\\xx\\xx\\Desktop\\Data\\xxxx.crt.pem")
except mysql.connector.Error as err:
print(str(err))
exit()
while executing the script am getting the below error

2055: Lost connection to MySQL server at xxxxxx.azure.com:3306', system error: 1 [SSL: NO_CIPHERS_AVAILABLE] no ciphers available (_ssl.c:997)

any help would be appriciated.

Unexpected error when calling purge command via execute (no replies)

0
0
Hello!

Running python3.8, mysql-connector-python 8.3.0, and mysql 8.0.35, I've run into something that I'm unsure qualifies as a bug, but at the very least I find strange behavior.

I've got some typical factory code that has 2 exactly-as-you'd-expect context-manager functions, one yields a database connection and the other uses that function to yield a cursor (for context for the next part).

-----
class DBConnectionFactory:
host: str
port: int
db: str
user: str
password: str

@contextlib.contextmanager
def connect(self) -> Iterator[mysql.MySQLConnection]:
conn = mysql.connect(
host=self.host,
port=self.port,
db=self.db,
user=self.user,
password=self.password,
)
conn.get_warnings = True
try:
yield conn
finally:
conn.close()

@contextlib.contextmanager
def cursor(self, dictionary: bool = False) -> Iterator[Cursor]:
with self.connect() as conn:
cur = conn.cursor(dictionary=dictionary)
try:
yield cur
finally:
cur.close()
-----



Attempting to run a PURGE BINARY LOGS command only works when run via the database connection:

-----
with db.connect() as conn:
conn.cmd_query(f"PURGE BINARY LOGS BEFORE '{start_time}';")
-----


Now, this is basically what the documentation dictates, but for the longest time, I was running it like this

-----
with db.cursor() as cur:
cur.execute(f"PURGE BINARY LOGS BEFORE '{start_time}';")
-----

because I did not understand that there was a difference at first. The "bug" behavior comes in with how mysql connector handles the response from the server. The purge command itself is run, I can validate it by listing the binary log files and asking mysql to SHOW BINARY LOGS. but the error comes in the stack trace.

-----
Traceback (most recent call last):
File "script.py", line 193, in flush_logs
cur.execute(f"PURGE BINARY LOGS BEFORE '{start_time}';")
File "venv/lib/python3.8/site-packages/mysql/connector/cursor.py", line 748, in execute
self._handle_result(self._connection.cmd_query(stmt))
File "/venv/lib/python3.8/site-packages/mysql/connector/cursor.py", line 614, in _handle_result
self._handle_noresultset(result)
File "/venv/lib/python3.8/site-packages/mysql/connector/cursor.py", line 585, in _handle_noresultset
self._handle_warnings()
File "/venv/lib/python3.8/site-packages/mysql/connector/cursor.py", line 1054, in _handle_warnings
warnings.warn(err, stacklevel=4)
TypeError: expected string or bytes-like object
-----

Best as I can tell, the warning handler for the cursor isn't prepared to handle the non-row response from the server. I confirmed that start_time was in fact a string, as well as the entire string I was passing to execute, so I looked into the source code and confirmed it was being thrown by the library.

Now, I'm not entirely sure what the best approach to this is. I'm unsure if it qualifies as a bug since I'm a) probably not supposed to be running the "Database level commands" like purge through execute and b) fully aware of the existence of cmd_query now

However, it seems like the library should either a) handle the error in a more pythonic manner since both approaches to actually run the command b) not let me run the command via execute or c) not throw an error at all.

I also verified that this error is only occurring after 8.0.12, as it doesn't throw an error at all with that version, but all subsequent versions throw the error. I'd be happy to file a bug request if this is considered a bug, but I figured I'd check in the forums before doing anything.

MySQL Asynchronous Connectivity with MySQL Connector/Python (no replies)





Latest Images