atlas: Unexpected view definition on v0.13.0

I managed my migrations for a Supabase instance using Atlas, and after the new version dropped, migrations stopped working.

I get this error while running supabase locally.

Error: unexpected empty view definition was returned for "extensions"."pg_stat_statements"

About this issue

Original URL
State: closed
Created a year ago
Comments: 16 (8 by maintainers)

Most upvoted comments

I pushed a fix and released a new binary. Would you mind pulling the new binary and report if that solved the issue?

a8m on Aug 9, 2023

Thanks for reporting this, @RD211. I’ll give this a look ASAP.

a8m on Aug 7, 2023

Great, it works fine now! Thanks a lot!

mcaxtrzen on Aug 9, 2023

Hey, @mcaxtrzen! I missed your previous comment.

Altas currently does not support materialized views (this should be added soon), and the inspection fails as Atlas can’t find the my_materialized_view (materialized) view as a dependency. I’ll send a patch to fix this and will let you know when it’s ready.

a8m on Aug 9, 2023

Hi! Thanks for the help with this!

Do you mean that a fix would be to only look at some of the schemas instead? If so, yeah, that should work for me. I am interacting with public but also with storage directly so that’s why I did not put a search_path but I suppose there is a way to select more than one schema.
Yes, I did not want to manage those at all, so I guess either ignoring them or not looking at all at those schemas could also work.

I found something in the docs to only look at some schemas, so I think I will try that, as that would be the easiest option.

Thanks a lot for the help!

RD211 on Aug 8, 2023