Hello,

We do not have any such caching, those tables simply do not exist in that database, have you ran the migrations on that specific database?

mysql> USE railway;

Database changed

mysql> SHOW COLUMNS FROM activity_log;

+-----------------+----------+------+-----+-------------------+-------------------+

| Field | Type | Null | Key | Default | Extra |

+-----------------+----------+------+-----+-------------------+-------------------+

| id | int | NO | PRI | NULL | auto_increment |

| user_id | int | NO | | NULL |

|

| timestamp | datetime | NO | | CURRENT_TIMESTAMP | DEFAULT_GENERATED |

| mouse_distance | float | YES | | NULL | |

| keystrokes | int | YES | | NULL | |

| mouse_clicks | int | YES | | NULL |

|

| idle_count | float | YES | | NULL | |

| page_time | json | YES | | NULL | |

| page_percentage | json | YES | | NULL | |

+-----------------+----------+------+-----+-------------------+-------------------+

9 rows in set (0.00 sec)

mysql>

I see it in mysql but railway is not pulling the two new columns "page_time" and "Page percentage"

try:

db = pymysql.connect(

host=DB_HOST,

user=DB_USER,

password=DB_PASSWORD,

database="railway", # FORCE SELECTION

cursorclass=pymysql.cursors.DictCursor,

autocommit=True

You have likely ran the migrations on the wrong database name.

I see your note about running migrations on the wrong database. However, I have manually verified that my MySQL instance has the correct schema, yet Flask still sees the wrong version.

I'm not sure what to tell you at this point, the page_time and page_percentage tables simply do not exist in the database, you can see for yourself -

https://railway.com/project/dfaa0ddf-a0e0-48f8-8ff1-b9ad7db934bc/service/3bae0b4c-6c6a-4083-8adc-21e96526e846/data?environmentId=8ffcc3b7-f7b7-4bab-adaf-a8acebb4cc57