-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database v1 tables not detected #3
Comments
I had the same error, I managed to solve it by upgrading to 1.40.0 first, then running the migration script. |
I had the same error too. After a long time debug, I found MySQL user used for umami don't have permission of DROP command. |
How do I do that? I changed the just from 1.33 to 1.40 and there seems to be some missing migrations. How do I run those? |
For anyone trying to migrate to 1.4 from previous versions, checkout the V1 branch and do |
I'm trying to upgrade from umami-software/umami@0cb14f3 (v 1.38 or so) to latest umami-software/umami@71bb012, but when running this migration tool, I'm seeing the following error.
The tables I have in supabase are as follows:
.
Upon reviewing the code, it seems to require a
v1_account
table and a04_add_uuid
migration. However, the table namedaccount
exists and only three migrations (01_init
, 02_add_event_data
, and03_remove_cascade_delete
) have been executed.Full Schema Below
The text was updated successfully, but these errors were encountered: