Skip to content
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

Open
nickradford opened this issue Jul 6, 2023 · 4 comments
Open

Database v1 tables not detected #3

nickradford opened this issue Jul 6, 2023 · 4 comments

Comments

@nickradford
Copy link

nickradford commented Jul 6, 2023

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.

image

The tables I have in supabase are as follows:
image.

Upon reviewing the code, it seems to require a v1_account table and a 04_add_uuid migration. However, the table named account exists and only three migrations (01_init, 02_add_event_data, and 03_remove_cascade_delete) have been executed.

Full Schema Below

table_name column_name data_type
_event_old website_id integer
_event_old created_at timestamp with time zone
_event_old event_id integer
_event_old event_value character varying
_event_old url character varying
_event_old session_id integer
_event_old event_type character varying
_prisma_migrations finished_at timestamp with time zone
_prisma_migrations started_at timestamp with time zone
_prisma_migrations migration_name character varying
_prisma_migrations checksum character varying
_prisma_migrations logs text
_prisma_migrations applied_steps_count integer
_prisma_migrations rolled_back_at timestamp with time zone
_prisma_migrations id character varying
account is_admin boolean
account updated_at timestamp with time zone
account created_at timestamp with time zone
account user_id integer
account username character varying
account password character varying
event session_id integer
event event_name character varying
event event_id integer
event url character varying
event website_id integer
event created_at timestamp with time zone
event_data event_data_id integer
event_data event_data jsonb
event_data event_id integer
pageview session_id integer
pageview created_at timestamp with time zone
pageview website_id integer
pageview view_id integer
pageview url character varying
pageview referrer character varying
session screen character varying
session os character varying
session created_at timestamp with time zone
session session_id integer
session session_uuid uuid
session language character varying
session website_id integer
session country character
session device character varying
session hostname character varying
session browser character varying
website website_id integer
website website_uuid uuid
website share_id character varying
website domain character varying
website created_at timestamp with time zone
website name character varying
website user_id integer
@mgolub2
Copy link

mgolub2 commented Jul 15, 2023

I had the same error, I managed to solve it by upgrading to 1.40.0 first, then running the migration script.

@MagmaBlock
Copy link

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.
OMG, why the migrator only print a Database v1 tables have not been detected., there is more error details needed

@ahopkins
Copy link

I had the same error, I managed to solve it by upgrading to 1.40.0 first, then running the migration script.

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?

@saravanapriyanm
Copy link

For anyone trying to migrate to 1.4 from previous versions, checkout the V1 branch and do yarn install and yarn build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants