Fix: Correctly drop and recreate claim_next_submission function

This commit is contained in:
gpt-engineer-app[bot]
2025-10-09 13:43:23 +00:00
parent 6ec5ca3bc4
commit 57368eb309
5 changed files with 56 additions and 39 deletions

View File

@@ -220,7 +220,6 @@ export type Database = {
id: string
locked_until: string | null
original_submission_id: string | null
priority: number
resolved_at: string | null
review_count: number | null
reviewed_at: string | null
@@ -246,7 +245,6 @@ export type Database = {
id?: string
locked_until?: string | null
original_submission_id?: string | null
priority?: number
resolved_at?: string | null
review_count?: number | null
reviewed_at?: string | null
@@ -272,7 +270,6 @@ export type Database = {
id?: string
locked_until?: string | null
original_submission_id?: string | null
priority?: number
resolved_at?: string | null
review_count?: number | null
reviewed_at?: string | null
@@ -2640,10 +2637,6 @@ export type Database = {
}
}
Functions: {
calculate_submission_priority: {
Args: { submission_id: string }
Returns: number
}
can_approve_submission_item: {
Args: { item_id: string }
Returns: boolean
@@ -2675,7 +2668,6 @@ export type Database = {
claim_next_submission: {
Args: { lock_duration?: unknown; moderator_id: string }
Returns: {
priority: number
submission_id: string
submission_type: string
waiting_time: unknown