> This is an issue with Metabase, but not rather an issue in how you insert values in the DB

Nobody has claimed this yet.

> This is not an issue with Metabase, but rather an issue in how you insert values in the DB

I think you did not carefully examine the issue I raised, and I have sufficient evidence to prove that it is a bug in Metabase.

1. Autocommit is disabled by default when connecting through Connector/Python.
Detail: https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlconnection-autocommit.html

2. Even if I set autocommit to off in MySQL, this issue still exists in Metabase.

3. During this process, I used MySQL Workbench, DBeaver, and Datagear to view the 'apple' and 'apple_view' tables in the database without encountering this issue.

4. You can spend a few minutes trying the operations mentioned in my previous issue. This problem occurs consistently, so if you're not familiar with Python or pymysql, you can seek assistance from someone who is.

_Originally posted by @dashi6174 in https://github.com/metabase/metabase/issues/35699#issuecomment-1815966811_

Start by reading the referenced issue #35699 and reproducing the reported table and view behavior with the mentioned MySQL Connector/Python or pymysql setup. Confirm the behavior before tracing the relevant Metabase database interaction; done requires a clear reproduction and an identified cause or testable fix.

Written by the indexing model from the issue text.