Hi. New to discord & Supabase. I was looking for ideas and came across this really awesome Twitter thread yesterday (@supabase had shared) with good ideas around Supabase. Just wanted to share: https://twitter.com/upen946/status/1559125261580488707

Not sure where to put this in all the channels, but when you upload something to a bucket it returns a key containing the bucket name and the file path of the object. so I have a bucket called

albums

and I uploaded a file to

artist/title.png

the key returned was

albums/artist/title.png

, I stored that and then tried to use it

from.getPublicUrl()

but the key is incorrect because it contains the bucket name. I think the response should be

{ bucket: string, key: string }

I would like to see an example of remote config with vanilla js

also I'm thinking of app development using Unity it would be beneficial if we see supabase have unity's sdk

i'd love to see cursor pagination for queries

Thoughts on adding https://github.com/begriffs/pg_rational to the list of supported PG extensions? I came by this extension from reading https://begriffs.com/posts/2018-03-20-user-defined-order.html

i d love to see cursor pagination for

the supabase docs suggest that you can destructure user/session/error from the sign in using spotify but these are always null for me -- is this correct?

#1006358244786196510 next time, I'm pretty sure it does work though

it feels like an oversight that cannot have more than one "Maker"

not directly related to supabase, but yeah

We just had a new developer use this. As a suggestion the NPM option could be updated or removed?

We just had a new developer use this As

Made with Supabase

Would be nice to have a guide to work with VSCode, examples common use cases.

Include some documentation about how Postgres auth works in the RPC section, because sometimes you might create a function that will run with the same perms of the authenticated user client-side at the time of running the function instead of the perms of the authenticated postgres user at the time of writing the function. I think RPCs fail silently when they don't have the required permissions/satisfy RLS to run the function to completion, so as a developer you might wonder what's wrong. The logs don't say anything about it either. TLDR: You have to write the function with

SECURITY DEFINER

to run the fn with perms to ignore RLS.

Hi everyone! Last time I suggested this open source project to make Postgres serverless https://github.com/neondatabase/neon someone said that the Supabase team will have a look at it. Did you already do this and are there plans for this? 🙂

Interesting...

I didn't even realize they had a "Serverless SQL" option in AWS. Interesting premise

My issues with v2: 1. My types may not always match the database, as I may do custom joins, or even join objects from the auth etc... getting rid of this ability is a problem for me:

supabase.from<Post>('posts').select('*')

... I don't see why the generics couldn't support both 2. Subscriptions a. The old V1 syntax is not supposed to be depreciated according to the release, but does not work b. This is way over complicated IMO. The channel name should just automatically generate a UUID where I don't have to name it unless I want to. In that case I would use the internal unsubscribe method. c. This is where Firebase is amazing. The syntax for subscriptions IMO should be easy and the same as the regular query. Even V1, the subscription and the query are completely different statements: -

this.supabase.from(col).select('*').eq(field, value).single()

- `this.supabase.from(

${col}:${field}=eq.${value}

).on('*', (payload) => {})` The select etc should look the same. I feel like this is over complicating something that should just work without thinking. In supabase's case, the statement should be the same... add the name of the channel if you want, add the event (default to *), default schema or select one if you want, then run the subscribe method... That being said, the changes to the auth methods will definitely be welcomed, although I have not tested them yet.

With regards to your #1 issue, I ended up extending each database type so that I could include joined objects. Not ideal, but using the tool still with that workaround saves a lot of work getting your types in parity with the db.

discord bot to auto-remove tokens accidentally sent not sure where it would be hosted but i would happily code something up i would imagine it would go something like this 1. upon every received message in a non-private channel, scan it with this regex for jwts (feel free to suggest a better one)

(ey[a-zA-Z0-9-_]{3,}\.[a-zA-Z0-9-_]{3,}\.[a-zA-Z0-9-_]{3,})

2. try to read the json body 3. if it's a service role token, delete the message, and dm the user explaining what happened with the original message (if dms fail, just send a message in the current channel, don't send the original message though) if it's an anon token, maybe send a warning to the user, and give them options like deleting the message, disabling the warning, or auto-deleting in the future

Can we get this merged? https://github.com/supabase/auth-helpers/pull/227 20 day and counting old PR to support next.js 12.2.x auth helpers.. currently blocked by this unless i downgrade next.js :/

authentication life cycle hooks for things like onUserCreate, onUserEmailVerified would be super handy for onboarding like aws cognito

I hope that when Prisma releases their support for multiple schemas (currently in progress), that supabase CLI switches to their introspection over pgadmin

For the

supabase-cli

it might be worth adding some error messages that are caused by a user not being authenticated with the CLI itself. Or maybe provide an error if you execute

supabase init

while not authenticated? For example I hadn't realised I wasn't authenticated (I work across multiple machines) and just spent a while trying to figure out why a brand new project was failing at the

Setting up the schemas...

step when running

supabase start

. I was getting an error message like

Error: Error response from daemon: Container f56929cce538b2ed6a23398439b324db82719287b011544b4ccf73fdd53915f4 is restarting, wait until the container is running

. This appears to happen if you run

supabase init

while unauthenticated.

Add an error code to check for aborted requests, that would be better than the actual solution which is to check for a "long" given string: https://supabase.com/docs/reference/javascript/select#aborting-requests-in-flight. Especially useful when a user disconnect from a device, hence aborting all the pending requests.

Could there be a custom tier for doing a GitHub sponsorship (get no benefits)?

Suggestion: It would be really useful to have some examples of supabase storage that aren't coupled with supabase user auth, the docs are a bit fragmented tbh + example repos couple user auth and storage very tightly... the implementation I needed is actually quite simple and going thru the

user-management

examples referenced in the storage docs did not really help

unfortunately have to go back to S3 for file storage, I was pretty psyched to be able to use Supabase storage but the complexity around secure uploads without using Supabase user auth is a deal-breaker. thanks for the great software anyway guys, hoping I can use this next time with secure upload URLs!