Dataframe.to_sql(.....) encounters table not exists

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dataframe.to_sql(…) 出现table not exists

| username: 不输土豆

To improve efficiency, please provide the following information. A clear problem description can help resolve the issue faster:

[Overview]
When using pandas.DataFrame.to_sql(…), an error is reported stating that the table does not exist. Moreover, the non-existent table is not the one I intend to write to.
The code is as follows:


Error content:

I intend to write to the event_base.XqbUser table, but the error reports that another db.table does not exist.

[Application Framework and Development Adaptation Business Logic]

[Background] Operations performed

[Phenomenon] Business and database phenomena

[Problem] Current issue encountered

[Business Impact]

[TiDB Version] V6.5.0

[Attachments] Relevant logs and monitoring

| username: TiDB_C罗 | Original post link

Is it the table in the query statement?

| username: 不输土豆 | Original post link

Is it the same case as this bug?

| username: 不输土豆 | Original post link

The tables that reported errors were most likely indeed nonexistent at the corresponding error times.

| username: 不输土豆 | Original post link

What does it mean?

| username: lmdb | Original post link

Pay attention

| username: tidb狂热爱好者 | Original post link

It should be the same bug.

| username: 考试没答案 | Original post link

User permissions have been sent. Also, please send the part about configuring the database in Django.

| username: 不输土豆 | Original post link

This does not involve the Django service, it just mistakenly reported Django-related tables.

| username: tidb狂热爱好者 | Original post link

Look at the impact of 6.5.

| username: Jjjjayson_zeng | Original post link

Upgrade to version 6.5.1

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.