Hello there! I'm using

supabase-js

and I found out that it would be great to have a way to convert the casing in responses (Postgres convention is

snake_case

  while JS's one is

camelCase

for example) to match the language's conventions. This is something that some ORMs provide, such as Objection https://vincit.github.io/objection.js/recipes/snake-case-to-camel-case-conversion.html In the meantime, I hacked a custom replacer using proxies:

js
function withCamelCase(builder) {
  return new Proxy(builder, {
    get: (target, prop, receiver) => {
      if (prop === "then") {
        return (...args) =>
          target
            .then((response) => ({
              ...response,
              data: camelCase(response.data, { deep: true }),
            }))
            .then(...args)
      }

      if (typeof target[prop] === "function") {
        return (...args) => withCamelCase(target[prop](...args))
      }

      return Reflect.get(target, prop, receiver)
    },
  })
}

export default () => {
  const client = createClient(SUPABASE_URL, SUPABASE_KEY)

  return withCamelCase(client)
}

On the 30 millions series a article I think there is a typo

At the end of the 1st paragraph, I think it should be "small part of the SB vision"

I recommend a discord channel for those seeking individual paid (or free) help with their actual database (not just general guidance). A relational database may work fine for the first few months, but can quickly deteriorate in performance if there is not a understanding of query cost, indexing, etc. I think this is a topic ignored in the docs (in particular when to index), that will eventually bite a fast growing website started by someone without experience in RDB tuning. It is also hard to even know what questions to ask or answer in a discord chat. Of course maybe this is part of Supabase's plan for add on service and support down the road, then ignore the channel idea. Love the product so far.

thanks for the suggestion Gary. We do actually have special support packages - we generally reach out to developers when we see their projects scaling up. We're still working on the support packages, but they generally hit the things you're asking for: - dedicated support staff - shared slack channel - help optimizing etc

Any chance to do purging for stored files in Supabase? Thanks ❤️

Hey, I wanted to check about Column Level Security - maybe you have some thoughts: in Firebase it's not possible to restrict what fields to return in a document unless you build a cloud function or something like that. What about Supabase? RLS looks great but the same issue I guess - how to restrict what columns can be returned? Only by building middleware or there are some other ways?

Column Level Security

I don't know if it's correct, but when I switch between tables in the table editor view, table data is getting fetched everytime when I switch to another table. I think this is bad UX. It'd better if

useSWR

is used for caching data. Just a thought 🙂

Hey, I have a suggestion, what do you think about auth using Telegram account?

Can you guys make a multi tenant example? Thanks!

Hello y’all curious if there has been any consideration to adding tiktok as an oauth provider ?

does supabase optimize stored items by de-duplicating them (using say sha256), or should we do that ourselves for our projects?

I think this is really a PostgreSQL question (since Supabase uses PostgreSQL as the underlying database and Supabase itself does NOT have any intermediate layer which would do that). If anyone here knows, feel free to jump in but my guess is that you would have better luck trying PostgreSQL-specific arenas (e.g. the official PostgreSQL IRC chennel). If I had to guess, PostgreSQL does NOT do that automatically - as far as I know, this is a technique usually employed by NoSQL dbs which do NOT encourage or support normalization and, hence, need a way to efficiently store data which is duplicated across documents

ah.. no 😅 I meant de-duplicate items in storage.buckets - images, videos and multimedia

so that if multiple users upload the same large file, it is only stored once in the backend, and has multiple references to it

aah, I see - I don't know, haven't used storage. In any event, I suggest asking that in #843999948717555735 or #839993398554656831

If all of the team has access to #867343329434664980 it would make it easier for contributors to contact the team with regards to contribution, open PRs or general queries so other contributors can see but it dosen't pollute public channels.

Contributing to Supabase

GROQ support could be nice to have. Less complex instead of GraphQL. https://groq.dev/

Any extra suggestions for this PR? https://github.com/supabase/gotrue/pull/269 The current 3 are all working and should be read for the team to merge!

@User @User Was chatting with Nader on a stream about authentication with Ethereum wallets. It came up that this would be dope to have as an auth method on Supabase and wanted to see if anyone was working on this or if I might be able to contribute this. We were going over an implementation of Ethereum auth I did for a workshop would love to see about adapting it for supabase

Web 3 auth

is this for supabase storage? If you delete the bucket/folder it should purge everything

Maybe they ment like having a TTL or saying delete all files over X days old

PLEASE catch command-S on the SQL screen, I literally can't not save.

When you create a new snippet via the SQL console on the dashboard, they're automatically saved

Yes, but I keep accidentally hitting command-s when i finish editing, which brings up the native save dialog, which is a huge waste of time

I'm honestly not trying to be antagonistic here, but simply pressing

Escape

should dismiss that dialog, doesn't it?