Skip to content

fix(db): explicitly create search functions in public schema #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zacharias-ona merged 1 commit into from
Apr 15, 2026
Merged

fix(db): explicitly create search functions in public schema #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 12 additions & 8 deletions supabase/migrations/20260415111351_add_page_search_vector.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,8 @@
-- Full-text search on pages: extract text from Lexical JSON, build tsvector, index with GIN.
--
-- All functions are explicitly created in the public schema so that
-- cross-function calls resolve correctly regardless of the session's
-- search_path (Supabase migration runners may use a non-public default).

-- =============================================================================
-- 1. Function to extract plain text from Lexical editor JSON
Expand All @@ -7,7 +11,7 @@
-- type = "text" under a "text" key. This function recursively walks the
-- JSON tree and concatenates all text values separated by spaces.

create or replace function extract_text_from_lexical(content jsonb)
create or replace function public.extract_text_from_lexical(content jsonb)
returns text
language plpgsql
immutable
Expand All @@ -32,14 +36,14 @@ begin
if children is not null and jsonb_typeof(children) = 'array' then
for child in select jsonb_array_elements(children)
loop
result := result || extract_text_from_lexical(child);
result := result || public.extract_text_from_lexical(child);
end loop;
end if;

-- Lexical wraps content in { root: { children: [...] } }
-- Handle the root wrapper
if content ? 'root' then
result := result || extract_text_from_lexical(content -> 'root');
result := result || public.extract_text_from_lexical(content -> 'root');
end if;

return result;
Expand All @@ -51,7 +55,7 @@ $$;
-- =============================================================================
-- Title gets weight A (highest), content text gets weight B.

create or replace function page_search_vector(title text, content jsonb)
create or replace function public.page_search_vector(title text, content jsonb)
returns tsvector
language plpgsql
immutable
Expand All @@ -69,23 +73,23 @@ $$;
-- 3. Generated column on pages table
-- =============================================================================

alter table pages
alter table public.pages
add column search_vector tsvector
generated always as (page_search_vector(title, content)) stored;
generated always as (public.page_search_vector(title, content)) stored;

-- =============================================================================
-- 4. GIN index for fast full-text search
-- =============================================================================

create index pages_search_idx on pages using gin (search_vector);
create index pages_search_idx on public.pages using gin (search_vector);

-- =============================================================================
-- 5. Search function — called via supabase.rpc('search_pages', ...)
-- =============================================================================
-- Returns matching pages within a workspace, ranked by relevance.
-- Includes a text snippet from the content for display in search results.

create or replace function search_pages(
create or replace function public.search_pages(
query text,
ws_id uuid,
result_limit integer default 20
Expand Down
Loading