cli VS sql-examples

You'll need to install the Supabase CLI in different ways depending on your OS, check out this guide for details and come right back here.

Recently, I noticed that in our remote project, the database storage schema has a migration not present when one sets up the local stack for development. Upon inspection, the Supabase CLI uses an old version of the storage image. Currently, there is no way to change this (that I know of) until the CLI team updates the CLI to use this version.

@doganugurlu Looks like Deno team implemented a fix https://denostatus.com/cllm0jzq219036bjottk03k2ac Are you still experiencing the issue?

We used to cache the modules locally, I will need to check if we made any configuration change. Can you kindly open an issue for Supabase CLI - https://github.com/supabase/cli/issues

> Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw.

Good point! will update the docs.

> Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338

I'll take a look at this issue. We've improved import map resolution in the last couple of CLI releases. But it looks like there are more edge cases.

We’ve moved the Supabase CLI to a fortnightly stable-release cycle. Every 2 weeks, we will update the latest tag on npm, the supabase/tap for homebrew, and the supabase scoop bucket. You can find the binary downloads in our GitHub latest release.

I think we've been working on that recently here: https://github.com/supabase/cli/pull/907

Can you try it locally with the supabase CLI? https://github.com/supabase/cli

For more info see this issue on GitHub.

I opened a Github issue: https://github.com/supabase/cli/issues/939, but I figured I'd see if any of you hit this and, hopefully, got past it.

Are there plans to support connections to self hosted remotes (to deploy to self-hosted instances, for example) with the cli? https://github.com/supabase/cli/issues/753

If you decide to do this we should put it on database.dev - i'm sure it would be very popular

database.dev fills the same role for PostgreSQL as npm for JavaScript or pip for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.

Supabase just wrapped up their Launch Week 7 with a ton of incredible features. This includes an AI assistant that was added to their premium platform. It is aware of your database design and can help you when creating more complex SQL queries. I'm even more thrilled by their most recent releases of outstanding open source projects, such as the PostgreSQL package manager database.dev. dbdev serves the same purpose for PostgreSQL that npm does for JavaScript. It gives your PostgresSQL database incredibly easy access to packages that give your DB superpowers like full-text search or one-time-only-read data access à la Snapchat. The best thing is that dbdev can load any PostgreSQL instance that has the required fundamental extensions, independent of the Supabase platform. Again, the code is open source. I can't wait to see where this project goes in the future, and I have no doubt that we will soon be able to utilize a lot more fantastic libraries. Like Brandon Roberts puts it:

hi hn!

supabase engineer and author of dbdev here

happy to answer questions

If you're looking for a next step after reading the article, checkout the available packages on https://database.dev

(shameless plug) https://database.dev/olirice/asciiplot is a fun one to play around with if you have some queries that could use optimization

I'm really looking forward to opening dbdev up to community packages in the coming weeks

https://database.dev/ Database for SQL commands - great for backend engineers!

If you - find it useful, please spare a 🌟 at the Github Repo If you - found any issue/bug, create issues is much appreciated. If you - wanted to contribute the SQL scripts, PR is even more welcomed!