Nielsien
12/02/2021, 10:34 AMegnus
12/02/2021, 10:36 AMegnus
12/02/2021, 10:36 AMfayaz
12/02/2021, 10:57 AMintegrations
where they can only only edit the data. basically each user to be linked with a object, which has the integrations data.
Use case - I want to capture the users UPI ID(a public payment handle in India), his google sheet id and his airtable base api key and ID, learning Supabase by building a finance tracker,
Note that there will be only one integrations row per user. Please let me know if I am doing this the wrong way.egnus
12/02/2021, 11:02 AMusers -> integration_id
and integrations -> user_id
and query in any direction like with the JS SDK supabase.from('users').select('*, integration:integration_id(*)')
and to edit with the SDK you can do like so supabase.from('integrations').update({OBJ TO UPDATE}).eq('user_id', USERID)
egnus
12/02/2021, 11:03 AMuser_id
and integration_id
as UNIQUE constraint and add index to them so queries run faster and the updates will work as expectedfayaz
12/02/2021, 11:03 AMfayaz
12/02/2021, 11:04 AMegnus
12/02/2021, 11:04 AMuser_id
from integrations
egnus
12/02/2021, 11:05 AMegnus
12/02/2021, 11:07 AMfayaz
12/02/2021, 11:07 AMegnus
12/02/2021, 11:08 AMegnus
12/02/2021, 11:09 AMIlko Kacharov
12/02/2021, 12:11 PMDeleted User
12/02/2021, 12:11 PMDeleted User
12/02/2021, 12:13 PMYelloJello
12/02/2021, 12:45 PMXyo
12/02/2021, 12:45 PMDeleted User
12/02/2021, 12:46 PMXyo
12/02/2021, 12:46 PMschniz
12/02/2021, 1:23 PMhidden
flag that flips (and should act like a DELETE statement)schniz
12/02/2021, 1:24 PMYelloJello
12/02/2021, 1:29 PMMuphet
12/02/2021, 1:34 PMfayaz
12/02/2021, 5:49 PMcreate table integrations (
id uuid references auth.users UNIQUE NOT NULL,
updated_at timestamp with time zone,
airtable_key text unique,
upi_handle text unique,
inserted_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL,
primary key (id)
);
user
12/02/2021, 6:11 PMXyo
12/02/2021, 6:16 PMMihai
12/02/2021, 6:27 PMekko
12/02/2021, 6:33 PMSELECT site.*
FROM site JOIN address ON site.address_id = address.id
ORDER BY address.name
postgrest issue here: https://github.com/PostgREST/postgrest/issues/1414
has anyone figured out a workout around for this yet? i'm thinking of just creating an rpc that takes in a direction param for the ordering