Filter based on a plpgsql function already defined

Greetings!

Consider the following scenario, i am fetching some content, from a db table

MusicSheets

MusicSheets

. The content should be accessible to authorized users, there are 3 columns in the MusicSheet to indicate the level of access,

everyone

everyone

friends_only

friends_only

and

just_me

just_me

. Following supabase best practices, the actualy sensitive information is stored on a separate table with solid policies. Now my problem is when listing the rows of

MusicSheet

MusicSheet

table on my UI, I don't really wanna rewrite all the functions i have already defined so my question is, can I reuse them in my filters client-level? Cheers!

Supabase•4y ago•

1 reply

praisethemoon

Filter based on a plpgsql function already defined

Greetings!

Consider the following scenario, i am fetching some content, from a db table

MusicSheets

MusicSheets

. The content should be accessible to authorized users, there are 3 columns in the MusicSheet to indicate the level of access,

everyone

everyone

friends_only

friends_only

and

just_me

just_me

. Following supabase best practices, the actualy sensitive information is stored on a separate table with solid policies. Now my problem is when listing the rows of

MusicSheet

MusicSheet

table on my UI, I don't really wanna rewrite all the functions i have already defined so my question is, can I reuse them in my filters client-level? Cheers!

Filter based on a plpgsql function already defined

Similar Threads

Filter based on a plpgsql function already defined

Similar Threads

Similar Threads

Similar Threads