Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions drizzle/0107_handy_sunset_bain.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
CREATE TABLE IF NOT EXISTS "cloud_pricing_catalog" (
"id" serial PRIMARY KEY NOT NULL,
"version" varchar(64) NOT NULL,
"currency" varchar(16) DEFAULT 'USD' NOT NULL,
"refreshed_at" timestamp with time zone,
"providers" jsonb NOT NULL,
"vendors" jsonb NOT NULL,
"model_count" integer DEFAULT 0 NOT NULL,
"synced_at" timestamp with time zone DEFAULT now()
);
--> statement-breakpoint
ALTER TABLE "model_prices" ALTER COLUMN "source" SET DEFAULT 'cloud';--> statement-breakpoint
CREATE INDEX IF NOT EXISTS "idx_model_prices_vendor" ON "model_prices" USING btree ((("price_data" ->> 'vendor')));--> statement-breakpoint
CREATE INDEX IF NOT EXISTS "idx_model_prices_aliases" ON "model_prices" USING gin ((("price_data" -> 'aliases')));

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 The file is missing a newline at end of file. Some migration tools and diff tooling warn on this.

Suggested change
CREATE INDEX IF NOT EXISTS "idx_model_prices_aliases" ON "model_prices" USING gin ((("price_data" -> 'aliases')));
CREATE INDEX IF NOT EXISTS "idx_model_prices_aliases" ON "model_prices" USING gin ((("price_data" -> 'aliases')));
Prompt To Fix With AI
This is a comment left during a code review.
Path: drizzle/0106_next_malcolm_colcord.sql
Line: 14

Comment:
The file is missing a newline at end of file. Some migration tools and diff tooling warn on this.

```suggestion
CREATE INDEX IF NOT EXISTS "idx_model_prices_aliases" ON "model_prices" USING gin ((("price_data" -> 'aliases')));
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Loading
Loading