mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
## Context Related to Dashboard Scalability, specifically having Postgres team as CODEOWNERS for dashboard queries This is just a clean up as we're currently piling manual queries into one folder under `data/sql/queries`, whereas I reckon it'll be better for each query to sit within their RQ folder for better context. Am opting the naming format for files housing queries to be `*.sql.ts`, and also updating CODEOWNERS to reflect as such Next step will also be to shift all the dashboard queries within pg-meta into studio itself as requested by the pg-meta team <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Consolidated and reorganized internal module structure for the data layer to improve maintainability and reduce redundancy. * Streamlined import paths across components to align with new consolidated module organization. * **Chores** * Updated code ownership patterns to reflect reorganized file structure. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Ali Waseem <waseema393@gmail.com>
21 lines
710 B
TypeScript
21 lines
710 B
TypeScript
import { sqlKeys } from '../sql/keys'
|
|
|
|
export const LARGEST_SIZE_LIMIT_BUCKETS_COUNT = 50
|
|
|
|
/**
|
|
* SQL to get the storage buckets with the largest file size limits.
|
|
*
|
|
* This query is unoptimized and should not be automatically called because
|
|
* there is no index on `file_size_limit` in the `storage.buckets` table.
|
|
*/
|
|
export const getLargestSizeLimitBucketsSqlUnoptimized = /* SQL */ `
|
|
SELECT id, name, file_size_limit
|
|
FROM storage.buckets
|
|
WHERE file_size_limit IS NOT NULL
|
|
ORDER BY file_size_limit DESC
|
|
LIMIT ${LARGEST_SIZE_LIMIT_BUCKETS_COUNT + 1};
|
|
`.trim()
|
|
|
|
export const getLargestSizeLimitBucketsKey = (projectRef: string | undefined) =>
|
|
sqlKeys.query(projectRef, ['buckets-with-largest-size-limit'])
|