github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-03-08 22:52:02 -05:00
Code Issues 5 Packages Projects Releases 8 Wiki Activity

[PR #257] [MERGED] Change Row Level Security #247

New Issue
Closed
opened 2025-10-31 17:00:25 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-10-31 17:00:25 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/257
Author: @ricoberger
Created: 5/2/2025
Status: ✅ Merged
Merged: 5/2/2025
Merged by: @ricoberger

Base: main ← Head: change-rlss

📝 Commits (1)

  • f8bb5f0 Change Row Level Security

📊 Changes

1 file changed (+20 additions, -0 deletions)

View changed files

➕ supabase/migrations/20250430093014_change_row_level_security.sql (+20 -0)

📄 Description

Change all defined row level security policies, to apply the new
performance recommendations by Supabase.

See https://supabase.com/docs/guides/database/database-advisors?queryGroups=lint&lint=0003_auth_rls_initplan

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/feeddeck/feeddeck/pull/257 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 5/2/2025 **Status:** ✅ Merged **Merged:** 5/2/2025 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `change-rlss` --- ### 📝 Commits (1) - [`f8bb5f0`](https://github.com/feeddeck/feeddeck/commit/f8bb5f0adb8f6b491a1ca2d0925134b1635019f4) Change Row Level Security ### 📊 Changes **1 file changed** (+20 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `supabase/migrations/20250430093014_change_row_level_security.sql` (+20 -0) </details> ### 📄 Description Change all defined row level security policies, to apply the new performance recommendations by Supabase. See https://supabase.com/docs/guides/database/database-advisors?queryGroups=lint&lint=0003_auth_rls_initplan <!-- Keep PR title verbose enough and add prefix telling about what source it touches e.g "[rss] Add feature xyz" or if the the PR is not realated to a source use "[core]", e.g. "[core] Fix xyz". If you add a breaking change within your PR you should add ":warning:" to the title, e.g. ":warning: [core] My breaking change" --> <!-- Description of what have been changed. Please also reference an issue, when available. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-10-31 17:00:25 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/feeddeck#247
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?