[jkcorrea]

First off, love everything Supabase is doing. Keep it up. A few blunt things off-the-bat:

1) pg.new is neat, but honestly I don't see why I'd use it when I can do the same thing directly inside my drizzle schema dir using Cursor's Composer UI, which has full context on my project. I know not many are using Cursor right now, but it's hard to fathom these kind of features don't become part-and-parcel of code editors soon..

2) I actually find it painful to have to login to Supabase on the web to manage the database. I never use the table editor, snippets, etc. I want a native app I can CMD+Tab to.

Don't mean to be rude, just objective so you can feel my pain as a user.

In terms of the Notebooks, yeah I meant like Jupyter Notebooks. I've experimented with having a shared Notion or markdown files committed to repos in order to

A) save & search for snippets of SQL for the team/future me

B) document the "why" along with each step in a playbook.

The issues with this are

1) its detached from our normal workflow and quickly becomes outdated relative to our schema/business needs

2) to run the queries you have to copypaste back into a SQL tool

3) queries are hardcoded for certain values. If I have a report I run daily, every day I have to go in and manually update the `row.timestamp BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'`, or if its a customer support workflow I have to replace the customer's ID everywhere. I'd rather have variables at the top I can reference throughout the queries, either as a code block like in Jupyter NB, or maybe some variable UI a la Insomnia/Postman

[saltcod]

> I actually find it painful to have to login to Supabase on the web to manage the database. I never use the table editor, snippets, etc. I want a native app I can CMD+Tab to.

I hear you on this part. Our customer base runs the entire spectrum from total beginner to db admin, so having GUI tools is important for a large chunk of people. That said, we want to make the experience objectively better for everyone in the spectrum.

[jkcorrea]

I'll also add, my gut preference would be for a tool built independent from Supabase. I don't/can't always use Supabase/postgres and even if some future Supabase db client was opened up to connecting to any db URL, I don't know how much I'd trust it not to be optimized for Supabase at the expense of the rest of the ecosystem if that makes sense.

Not that that should stop you from trying of course :)

[saltcod]

For sure Building a stand-alone client isn't in the plan at the moment, but that doesn't mean we shouldn't incorporate all the good ideas and make our Dashboard great :^)