Skip to content

fix: update ownership of database tables to CURRENT_USER#6959

Open
Shivam-nagar23 wants to merge 1 commit into
mainfrom
fix-ownership-transfer
Open

fix: update ownership of database tables to CURRENT_USER#6959
Shivam-nagar23 wants to merge 1 commit into
mainfrom
fix-ownership-transfer

Conversation

@Shivam-nagar23
Copy link
Copy Markdown
Member

@Shivam-nagar23 Shivam-nagar23 commented May 11, 2026

Description

Fixes #

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


Summary by Bito

  • Changed ownership of multiple database tables and sequences from 'postgres' to 'CURRENT_USER' in the SQL migration script.
  • Affected objects include app, app_env_linkouts, app_id_seq, app_level_metrics, app_store, and their associated sequences.

@github-actions
Copy link
Copy Markdown

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

@github-actions
Copy link
Copy Markdown

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
10.1% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant