postgres_lsp VS basejump

Thank you for turning me on top Cornucopia, it looks awesome. I've used the very similar aiosql in Python, but I hadn't realized there was a Rust analog.

To tell the truth I've been waiting for postgres_lsp to mature before trying it out, but based on this example [1] I think it does support multiple queries.

Since it uses a parser extracted from Postgres, the nonstandard syntax would probably trip it up, but there's probably a way to fix that.

[1] https://github.com/supabase/postgres_lsp/blob/main/example/f...

Cool. How does this compare to SafeQL, PgTyped, and Postgres language server ?

While code editors have great support for most programming languages, SQL support is underwhelming. We want to make Postgres as simple as Python. Our recently announced Postgres Language Server takes us a step in that direction - eventually it will provide first-class support for Postgres in your favorite code editor including Linting, Syntax Highlighting, Migrations Parsing, SQL Auto-complete, and Intellisense.

Postgres Language Server

To make life even easier, our friends at Basejump have created an entire suite of Supabase Test Helpers which make it simple to create users, run tests as an authenticated user, and test your RLS policies.

I'm trying to run a script npm run sync-stripe for this Next.js - Supabase starter project and I keep getting an error but I can run project locally and login/signup with supabase auth, which means nothing wrong in my .env file. What could this error be?

You can check out how I've handled this using accounts over at https://github.com/usebasejump/basejump. Under supabase/migrations, you can view the accounts migration file. Basically, users can have permission levels that dictate what account data they can access.