Jinni
04/18/2023, 7:54 AMlaznic
04/18/2023, 9:07 AMts
supabase.from('table')
.select('id, subquery(*)')
.eq('matches', true)
// Get only table entries where this subquery is an empty, WHERE NOT EXISTS or such
.filter('subquery.table_id', '???')
.limit(1)
lake_mattiato
04/18/2023, 9:27 AMhgseo16
04/18/2023, 9:51 AMgotrue-py
. If anyone could help me with this, I would really appreciate it!
cc. @UserLove3000
04/18/2023, 10:48 AMhttps://cdn.discordapp.com/attachments/1097835936286511184/1097835936475259010/image.png▾
zaibyeu
04/18/2023, 12:11 PMMerovingian
04/18/2023, 12:43 PMbesimon
04/18/2023, 1:01 PMhttps://cdn.discordapp.com/attachments/1097869581185454172/1097869581823000616/Screenshot_2023-04-18_at_10.57.51_pm.png▾
Ramboo_018
04/18/2023, 2:58 PMMATTI
04/18/2023, 3:03 PMhtml
<p>Token: {{ .Token }}</p>
Or am i supposed to do something else?
I am reading through this: https://supabase.com/docs/guides/auth/auth-email-templates#limitationsgaryaustin
04/18/2023, 3:34 PMcptCrunch
04/18/2023, 3:32 PMStuster
04/18/2023, 3:38 PMwuh
04/18/2023, 4:22 PMirreal
04/18/2023, 4:36 PM{"code":400,"msg":"SAML Assertion is not valid"}
. looking at auth logs in the supabase dashboard, i see: "error": "cannot validate signature on Assertion: Could not verify certificate against trusted certs"
What are my next steps? From reading the docs, it seems that Supabase should see the Certificate Azure AD is using at the point when I setup sso and pass the metadata xml. It should use that certificate to verify incoming requests, but it seems to not be doing that?goetzrobin
04/18/2023, 5:09 PM{
"code": 500,
"message": "LOGFLARE_API_KEY env variables are not set"
}
I cannot find documentation on how to get this API key. I also had hoped to be able to run the logging locally without having to sign up for a “3rd party” solution. Of course, I am willing to do that for a production or if I simply understand better how the integration works and what cost I can expect for running my local environment.
The exact issue is also laid out here: https://github.com/supabase/supabase/issues/13729
Thanks already for any help or pointers!ven
04/18/2023, 5:33 PMdatasource db {
provider = "postgresql"
url = env("DATABASE_URL")
shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
schemas = ["public", "auth"]
}
model User {
id String @id
email String @unique
Profile Profile?
@@schema("auth")
}
model Profile {
id Int @id @default(autoincrement())
user User @relation(fields: [supabase_uid], references: [id])
supabase_uid String @unique
email String
display_name String?
memberships Membership[]
@@map("profile")
@@schema("public")
}
Mirik
04/18/2023, 6:48 PMSubh
04/18/2023, 7:26 PMIlgrand
04/18/2023, 7:29 PMEge
04/18/2023, 7:33 PMAtrox
04/18/2023, 7:55 PMuser_metadata
but the user session does not reflect changes made via updateUser
.
I see the data in the database, but have to log out and back in to have it in the server session.squallsama
04/18/2023, 7:56 PMinvites
tables with invite_from
and invite_to
and user_profile
table with user_id
column that is foreign key for invite_from
and invite_to
.
I tried to do something like this:
.from('user_profile')
.select('*, invites!inner(invite_from(*))')
.eq('invites.invite_from', currentUserId)
But i got an exception:
Unhandled Exception: PostgrestException(message: Could not embed because more than one relationship was found for 'user_profile' and 'invites'
Try changing 'friendship_invites' to one of the following: 'invites!invites_invite_from_fkey', 'invites!invites_invite_to_fkey'. Find the desired relationship in the 'details' key.
Could you please explain what is a proper way ?𝕷𝖎𝖌𝖍𝖙𝖇𝖚𝖑𝖇
04/18/2023, 8:06 PMhttps://cdn.discordapp.com/attachments/1097976557500366998/1097976557722685510/image.png▾
https://cdn.discordapp.com/attachments/1097976557500366998/1097976557991112824/image.png▾
neiled
04/18/2023, 9:21 PMhttps://cdn.discordapp.com/attachments/1097995334287904859/1097995334686359663/image.png▾
mushzinho
04/18/2023, 9:25 PMMissTitanK3
04/18/2023, 10:20 PMtk
04/18/2023, 10:24 PMconst { data: appearanceIds, error: appearanceIdsError } = await supabase
.from('appearance_participants')
.select('appearance_id')
.eq('leader_id', person.leader_id)
if (appearanceIdsError) {
console.error('Error fetching appearance IDs:', appearanceIdsError.message);
}
I then use these returned appearance_Ids to get details on the appearances. One problem arises when a person has too many appearances and I get the URI is too long. I tried creating chunks of data so that everything loads, but could then get that to work with the load on scroll that is implemented into this page. Does anyone have any idea on how to get this to work?
right now this works for users who do not have many appearances but we get URI too long for people with a lot of appearancesEbenezer Don
04/18/2023, 10:26 PMhttps://cdn.discordapp.com/attachments/1098011591376646315/1098011591556993045/Screenshot_2023-04-18_at_17.32.12.png▾