Giter Club home page Giter Club logo

Comments (6)

sweatybridge avatar sweatybridge commented on July 24, 2024 1

I've fixed this regression npx supabase@beta db diff. Apologies for the inconvenience.

from supabase.

encima avatar encima commented on July 24, 2024

Hey hey, thanks for opening!

By default, the migrations commands exclude system schemas but it can include them if it is run with -s. Was it ever run to include the _analytics schema or is this included consistently when you run commands like db dump or db pull?

I cannot reproduce but this does not mean it is not a bug! Just want to sanity check first that _analytics was never included. You can check this in your terminal history (ctrl+r) will allow you to search.

from supabase.

stefan-girlich avatar stefan-girlich commented on July 24, 2024

I only used -s public once with supabase db dump, but this did not affect migrations created afterwards. _analytics was never included explicitly. The migration just prior to the faulty one did not contain _analytics.

Happy to share a debug log if there is a way to exclude private/organization data.

from supabase.

HoekWax avatar HoekWax commented on July 24, 2024

Hello, I have the same issue, I created a new project online, then linked it to a local projet, pulled the db. I then enabled "analytics" in config.toml then ran "db diff" to create a migration file which should not contain anything because it's a brand new project with nothing added but it does contain the definitions for the table _analytics.

from supabase.

stefan-girlich avatar stefan-girlich commented on July 24, 2024

Just upgraded my local environment to v1.167.4 (CLI); issue still exists.
When I create a new migration (e.g. supabase db diff -f add_output_tables --use-migra), the log output explicitly says that the extra schemas are included:

Diffing schemas: _analytics,_realtime,extensions,public

When I add -s public, the log will state Diffing schemas: public, but the actual migration file will still contain the extra schemas.

Update: It now worked as expected using -s public, still failing without.

from supabase.

SuperstrongBE avatar SuperstrongBE commented on July 24, 2024

I have the exact same issue today.
Thank @stefan-girlich for the workaround.
But internal schema should be excluded while creating migration.

from supabase.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.