pg_graphql VS storage

Hi, I'm the author of Supabase GraphQL (pg_graphql)

One of the restrictions of composite types is that they can not contain an instance of themselves. So unfortunately, this is not currently possible.

I had this issue when trying to implement an AST type for pg_graphql[1] back when it was written in SQL [2]. In the end we used a JSON type which was much less constrained. That might be solvable using pg_jsonschema [3] if you really wanted to have a good time though

[1] https://github.com/supabase/pg_graphql

It’s something that’ll come in future, but nothing available yet: https://github.com/supabase/pg_graphql/issues/17

But... If you're looking for Graphql/Postgres, maybe look at https://github.com/supabase/pg_graphql which popped onto my radar yesterday, but I have no experience with it.

Check out some of the generated queries this extension [1] pumps out and you might have an answer.

[1] https://github.com/supabase/pg_graphql

hey HN, supabase ceo here. I'm really excited about this release.

Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL API depending who is "logged in".

On Supabase, the extension is served via PostgREST[1] using the public PostgreSQL function exposed by pg_graphql. PostgREST exposes PG functions as RPC routes (in our case we also map /rest/v1/rpc/graphql => /graphql/v1)

I'll ping the main dev (@oli_rice) and make sure he is here to answer any technical questions. This is just one of the exciting features we're launching this week. Stay tuned for one of our most-requested features later this week.

[0] pg_graphql: https://github.com/supabase/pg_graphql

[1] PostgREST: https://postgrest.org/

[3] https://github.com/supabase/storage/issues/439

The Supabase Storage Engine is fully open source and is one of the few storage solutions that offer 3 interoperable protocols to manage your files:

For instance, consider a supabase setup where you place your photos in storage and your orders in a table. Then, have a function run automatically whenever a new row is added to the orders table. That function would be responsible for identifying what the customer bought and delivering it to them.

In this page, I used Supabase Storage to store the files uploaded by the users

-- Create a table for public profiles CREATE TABLE profiles ( id UUID REFERENCES auth.users ON DELETE CASCADE PRIMARY KEY, updated_at TIMESTAMP WITH TIME ZONE, username TEXT NULL, full_name TEXT, profile_image_url TEXT, bio TEXT, sex SMALLINT DEFAULT 0, CONSTRAINT username_length CHECK (CHAR_LENGTH(username) >= 3) ); -- Create a table for channeles CREATE TABLE channeles ( id SERIAL PRIMARY KEY, userRefId UUID REFERENCES auth.users(id), channel TEXT, updated_at TIMESTAMP WITH TIME ZONE ); -- Create a table for geo location CREATE TABLE user_geo ( id SERIAL PRIMARY KEY, userRefId UUID REFERENCES auth.users(id), location GEOGRAPHY(point) NOT NULL, updated_at TIMESTAMP WITH TIME ZONE ); create index user_geo_index on public.user_geo using GIST (location); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE profiles ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public profiles are viewable by everyone." ON profiles FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own profile." ON profiles FOR INSERT WITH CHECK (auth.uid() = id); CREATE POLICY "Users can update own profile." ON profiles FOR UPDATE USING (auth.uid() = id); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE channeles ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public channeles are viewable by everyone." ON channeles FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own channeles." ON channeles FOR INSERT WITH CHECK (auth.uid() = userRefId); CREATE POLICY "Users can update own channeles." ON channeles FOR UPDATE USING (auth.uid() = userRefId); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE user_geo ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public geo_location are viewable by everyone." ON user_geo FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own geo_location." ON user_geo FOR INSERT WITH CHECK (auth.uid() = userRefId); CREATE POLICY "Users can update own geo_location." ON user_geo FOR UPDATE USING (auth.uid() = userRefId); -- See https://supabase.com/docs/guides/auth/managing-user-data#using-triggers for more details. CREATE OR REPLACE FUNCTION public.handle_new_user() RETURNS TRIGGER AS $$ BEGIN INSERT INTO public.profiles ( id, updated_at, username, full_name, profile_image_url, bio, sex, ) VALUES ( NEW.id, NOW(), NEW.raw_user_meta_data->>'username', NEW.raw_user_meta_data->>'full_name', NEW.raw_user_meta_data->>'profile_image_url', NEW.raw_user_meta_data->>'bio', COALESCE(CAST(NEW.raw_user_meta_data->>'sex' AS SMALLINT), 0), ); INSERT INTO public.channeles (userRefId, channel, updated_at) VALUES (NEW.id, NEW.raw_user_meta_data->>'expoToken', NOW()); INSERT INTO public.user_geo (userRefId, location, updated_at) VALUES ( NEW.id, ST_Point(CAST(NEW.raw_user_meta_data->>'lat' AS FLOAT), CAST(NEW.raw_user_meta_data->>'lng' AS FLOAT)), NOW() ); RETURN NEW; END; $$ LANGUAGE plpgsql SECURITY DEFINER; CREATE TRIGGER on_auth_user_created AFTER INSERT ON auth.users FOR EACH ROW EXECUTE FUNCTION public.handle_new_user(); -- Set up Storage! INSERT INTO storage.buckets (id, name) VALUES ('profile_images', 'profile_images'); -- Set up access controls for storage. -- See https://supabase.com/docs/guides/storage#policy-examples for more details. CREATE POLICY "profile_image images are publicly accessible." ON storage.objects FOR SELECT USING (bucket_id = 'profile_images'); CREATE POLICY "Anyone can upload a profile_image." ON storage.objects FOR INSERT WITH CHECK (bucket_id = 'profile_images');

For example the storage-api. I was on version supabase/storage-api:v0.29.1 for a long time, until I realized, that there is a new version of it (0.40.1). Fast forward, upgraded everything, checked my application and everything storage related stopped working. From now on it's always the same procedure. Debugging the errors, digging through the code on GitHub, checking commits, issues, etc. After a while I found a bug from 2019 which had exactly the same error as I, tested the workaround and it worked again (partially, workaround).

Alternatively, we could use imagemagick (cli tool for image transforms) + supabase storage to do the same for free.

[5] https://supabase.com/docs/guides/storage

Storage

We'll probably need to upload other types of assets in the future, so having a way to set the limit per bucket would be nice... There's an issue for this - I may make a PR to implement it at some point.