I’m experiencing an issue with my project where PostgREST is still detecting a dropped foreign key.
I have already run:
NOTIFY pgrst, 'reload schema';
but the error persists:
Could not embed because more than one relationship was found for 'tickets' and 'events'
I’ve confirmed there are no views or materialized views referencing the old foreign key. I have reloaded the app multiple times but the issue still stands - it is detecting a non-existent old foreign ket relationship.
Is there another way to clear PostgREST’s cached metadata so the new schema is recognized correctly?