A suggestion: Permissions for the access tokens so users can give external apps access to their account on their behalf

compiled examples of application-level authorization approaches (acl, rbac, zanzibar) with instructions for usage

a suggestion: Why not Supabase company goes public (IPO) so we “the individual project believers” can buy stocks, I really wanted to invest in supabase but unfortunately it’s a private company.

supabase stonks only go up 😄

Not all companies need not should be public companies.

yes I understand because there are few requirements for reporting, but in my opinion for a project like this it worth, take Cloudflare for example it’s public and that only helped.

I'd also point out that Cloudflare was 9 years old when it went public, young companies benefit from not being public when they are still growing, Supabase is only 2 years (Afaik)

there is pros and cons in both, i don’t have enough knowledge to say which is best, so it was just a suggestion that will help them raise capital

there is pros and cons in both i don’t

I would like to see "pay as you go" plan. I don't need resources provided by 20$ plan. I want to pay for what I use. And I would like more integrations with payment methods and email marketing

I would suggest more videos or boilerplates about local development around supabase, I see so many repo's on GitHub of projects where developers could really leverage local supabase database + migrations. The power behind the local supabase cli is powerful and not being utilised by many.

Pay as you go plan

I'd like to suggest creating structured documentation for Database Webhooks on a dedicated page, even if they're still in Alpha status. Perhaps at https://supabase.com/docs/guides/database/webhooks Taking the Database Webhooks section at https://supabase.com/blog/supabase-functions-updates#database-webhooks-alpha would be a great starting point, but having things at a dedicated location would make the information much easier to google. I just spent 20 minutes figuring out that for DELETE queries, the deleted row in the hook payload is called

old_record

rather than

record

as it is with INSERT queries.

Export these types:

ts

/**
 * Error format
 *
 * {@link https://postgrest.org/en/stable/api.html?highlight=options#errors-and-http-status-codes}
 */
export type PostgrestError = {
  message: string
  details: string
  hint: string
  code: string
}

/**
 * Response format
 *
 * {@link https://github.com/supabase/supabase-js/issues/32}
 */
interface PostgrestResponseBase {
  status: number
  statusText: string
}

interface PostgrestResponseSuccess<T> extends PostgrestResponseBase {
  error: undefined
  data: T[]
  count: number | undefined
}
interface PostgrestResponseFailure extends PostgrestResponseBase {
  error: PostgrestError
  data: undefined
  count: undefined

Add some sort of dark theme to the status page, the main website is dark theme it would make sense for the status page to also be dark theme. (This is possible with the atlassin custom theming thingy)

I have a client asking about biometric auth in the future. Is that feature currently on the roadmap for Supabase?

Biometric

Uniformize error types to be either null or undefined on the types below (apply the same concept to data types)

ts
export interface PostgrestResponseSuccess<T> extends PostgrestResponseBase {
    error: undefined
    data: T[]
    count: number | undefined
}

export interface PostgrestResponseFailure extends PostgrestResponseBase {
    error: PostgrestError
    data: undefined
    count: undefined
}

export interface PostgrestSingleResponseSuccess<T> extends PostgrestResponseBase {
    error: undefined
    data: T
    count: number | undefined
}

export type SupabasePostgresqlResponse = PostgrestResponse<any> | PostgrestSingleResponse<any>

export type SupabaseStorageResponseSuccess = {
    data: Blob
    error: null
}

export type SupabaseStorageResponseFailure = {
    data: null
    error: StorageError | StorageApiError | StorageUnknownError
}

That is annoying to deal sometimes with null and sometimes with undefined, it should be only 1 of them

Not really sure where to post this but the dashboard is pretty broken on iPhone 12, iOS 16.1. Just thought I’d get it to your attention 🙂 I can’t get to the right most panel.

I'm wondering if there is any no-code tool to generate supabase triggers? Like have them in normal language (when x happens I want y to happen in the z table). Would be great to be able to link all flows visually.

Kind of like https://supabase-schema.vercel.app/ but actually be able to make new connections, not just view the connections.

If not, I'd really want to built it, if a backend dev wants to help out. It can even be a freemium product if that's an extra incentive, or just something open source for our portfolios.

I'm trying to figure out how to get RLS-filtered (RLS-authorized) realtime data from Supabase. According to the docs, the Realtime API does not use Postgres RLS rules, so it can't really be used for streaming data that requires RLS-authorization, on the other hand pg_graphql does not seem to provide streaming subscriptions. Did I overlook something?

I'm working on a platform to create 0 config preview environments for developers. Will it be possible to get some early stage feedback and suggestions from community members on my product?

Feedback on product

well how about us. we are not no code but we are LOW code. please check out our gitbub and lmk what do u think.https://github.com/illa-family

Bug!! I'm not sure where to put this. When creating a database password, there is no regex to check if the password would be a valid password or not. Special characters like "&" need to be caught and rejected because they don't work.

I think they are allowed, but you have to encode them to use them in a connection URL.

For MySQL, PostgreSQL and CockroachDB you must percentage-encode special characters in any part of your connection URL

Took me a bit to realise there's a checkbox when double clicking a bool cell in the database view. It was unchecked, so it didn't have enough contrast with the background.

Hi remc, Have you got a screenshot of this?