You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current database initial_create and initial_migrate, it might be better to make it so when you create a database table, it is created using the initial_create sql in the table, but at the current max version of that database table. Then if there is an update that changes the database, and the bot is installed, it simply creates the tables correctly, without immediately modifying them. Then if the database version is incorrect for bots that already exist, the migration is run. It seems like that is more straightforward than keeping a database table creation that is never needed.
The text was updated successfully, but these errors were encountered:
With the current database initial_create and initial_migrate, it might be better to make it so when you create a database table, it is created using the initial_create sql in the table, but at the current max version of that database table. Then if there is an update that changes the database, and the bot is installed, it simply creates the tables correctly, without immediately modifying them. Then if the database version is incorrect for bots that already exist, the migration is run. It seems like that is more straightforward than keeping a database table creation that is never needed.
The text was updated successfully, but these errors were encountered: