The server log has an exception:
ERROR 2022-03-24 11:45:44,047 [Stardog.Executor-187] com.complexible.stardog.serf.mysql.SerfServer:handleClient(288): BI/SQL server frontend error
java.lang.NullPointerException: utf8mb4
The client side:
OperationalError: (2013, 'Lost connection to MySQL server during query')
The above exception was the direct cause of the following exception:
OperationalError Traceback (most recent call last)
/var/folders/rg/jrpg2c9d2wsc593l608kj85h0000gp/T/ipykernel_29493/3433910095.py in <module>
3 engine = create_engine("mysql+pymysql://anonymous:password@host.com:5806/Topology")
4 sql = "show tables"
----> 5 df = pd.read_sql(sql, engine)
6 df
As the name implies, the BI/SQL interface is indented to be used with BI tools. From your code snippet you posted, it looks like you're trying to read Stardog data into a dataframe. We'd recommend doing this using pystardog, our Python library, to do so. You can find the documentation for it here: pystardog — pystardog documentation. On its Github page, you can also find an example Jupyter notebook.
Thanks for the log file. The issue we're having here is related to some MySQL-specific calls made by sqlalchemy around character sets and data types that we currently do not support.
BI/SQL JDBC connector support for sqlalchemy is a very desirable feature.
The recent Release of Pandas only support sqlalchemy and has deprecated the above example code.
So without sqlalchemy support, Stardog would not be able to claim it supported a python interface.