[pull] master from supabase:master

apps/docs/content/guides/ai/structured-unstructured.mdx

@@ -24,7 +24,7 @@ values
   ('79409372-7556-4ccc-ab8f-5786a6cfa4f7', array[0.1, 0.2, 0.3], 'Hello world', '/hello-world');
 ```
 
-Notice that we've associated two pieces of metadata, `content` and `url`, with the embedding. Those fields can be filtered, constrained, indexed, and generally operated on using the full power of SQL. Structured metadata fits naturally with a traditional Supabase application, and can be managed via database [migrations](/docs/guides/getting-started/local-development#database-migrations).
+Notice that we've associated two pieces of metadata, `content` and `url`, with the embedding. Those fields can be filtered, constrained, indexed, and generally operated on using the full power of SQL. Structured metadata fits naturally with a traditional Supabase application, and can be managed via database [migrations](/docs/guides/deployment/database-migrations).
 
 ## Unstructured
 

apps/docs/content/guides/database/postgres/column-level-security.mdx

@@ -82,7 +82,7 @@ You can view and edit the privileges in the [Supabase Studio](https://supabase.c
 
 ## Manage column privileges in migrations
 
-While you can manage privileges directly from the Dashboard, as your project grows you may want to manage them in your migrations. Read about database migrations in the [Local Development](https://supabase.com/docs/guides/getting-started/local-development#database-migrations) guide.
+While you can manage privileges directly from the Dashboard, as your project grows you may want to manage them in your migrations. Read about database migrations in the [Local Development](https://supabase.com/docs/guides/deployment/database-migrations) guide.
 
 <StepHikeCompact>
 

apps/docs/content/guides/deployment/branching.mdx

@@ -339,7 +339,7 @@ You can create new migrations either [locally](#develop-locally) or [remotely](#
 >
 <TabPanel id="local-dev" label="Local Development">
 
-The Supabase CLI provides two options: [manual migrations](https://supabase.com/docs/guides/cli/local-development#database-migrations) and [generated migrations](https://supabase.com/docs/guides/cli/local-development#diffing-changes) using Supabase's local studio and the `supabase db-diff` command. Let's use the latter and push the change to our Preview Branch:
+The Supabase CLI provides two options: [manual migrations](https://supabase.com/docs/guides/deployment/database-migrations) and [generated migrations](https://supabase.com/docs/guides/deployment/database-migrations#diffing-changes) using Supabase's local studio and the `supabase db-diff` command. Let's use the latter and push the change to our Preview Branch:
 
 <StepHikeCompact>
 

apps/docs/content/guides/deployment/maturity-model.mdx

@@ -8,15 +8,15 @@ Supabase is great for building something very fast _and_ for scaling up. However
 
 ## Prototyping
 
-The Dashboard is a quick and easy tool for building applications while you are prototyping. That said, we strongly recommend using [Migrations](/docs/guides/getting-started/local-development#database-migrations) to manage your database changes. You can use our CLI to [capture any changes](/docs/reference/cli/supabase-db-diff) you have made on the Dashboard so that you can commit them a version control system, like git.
+The Dashboard is a quick and easy tool for building applications while you are prototyping. That said, we strongly recommend using [Migrations](/docs/guides/deployment/database-migrations) to manage your database changes. You can use our CLI to [capture any changes](/docs/reference/cli/supabase-db-diff) you have made on the Dashboard so that you can commit them a version control system, like git.
 
 ## Collaborating
 
 As soon as you start collaborating with team members, all project changes should be in version control. At this point we strongly recommend moving away from using the Dashboard for schema changes. Use migrations to manage your database, and check them into your version control system to track every change.
 
 Resources:
 
-- [Database migrations](/docs/guides/getting-started/local-development#database-migrations)
+- [Database migrations](/docs/guides/deployment/database-migrations)
 - [Managing access on the Dashboard](/docs/guides/platform/access-control)
 - [PGAudit for Postgres](/docs/guides/database/extensions/pgaudit)
 
@@ -33,7 +33,7 @@ Once your application is live, you should never change your database using the D
 
 Resources:
 
-- [Database migrations](/docs/guides/getting-started/local-development#database-migrations)
+- [Database migrations](/docs/guides/deployment/database-migrations)
 - [Managing access on the Dashboard](/docs/guides/platform/access-control)
 - [PGAudit for Postgres](/docs/guides/database/extensions/pgaudit)
 - [Managing environments](/docs/guides/cli/managing-environments)

apps/docs/content/troubleshooting/why-is-my-camelcase-name-not-working-in-postgres-functions-or-rls-policies-EJMzVd.mdx

@@ -2,7 +2,8 @@
 title = "Why is my camelCase name not working in Postgres functions or RLS policies?"
 github_url = "https://github.com/orgs/supabase/discussions/12893"
 date_created = "2023-03-08T16:26:51+00:00"
-topics = ["database"]
+topics = [ "database" ]
+database_id = "9dbcf760-7b1f-4cc4-8653-4e884fd02dad"
 ---
 
 Avoid camelCase (upper case letters) if possible when naming functions, tables, columns, and variables. You must enclose "camelCase" in double quotes when you define it or use it. YOU WILL FORGET. Use snake_case instead and make your life easier.

apps/studio/components/interfaces/SQLEditor/DownloadSnippetModal.tsx

@@ -104,7 +104,7 @@ const DownloadSnippetModal = ({ id, ...props }: DownloadSnippetModalProps) => {
           <div className="flex justify-between items-center gap-x-2">
             <Button asChild type="default" icon={<ExternalLink strokeWidth={1.5} />}>
               <Link
-                href="https://supabase.com/docs/guides/cli/local-development#database-migrations"
+                href="https://supabase.com/docs/guides/deployment/database-migrations"
                 target="_blank"
                 rel="noreferrer"
               >

apps/studio/pages/project/[ref]/database/migrations.tsx

@@ -27,7 +27,7 @@ const MigrationsPage: NextPageWithLayout = () => {
         <ScaffoldSectionDetail className="flex items-center justify-end gap-x-2">
           <DocsButton
             className="no-underline"
-            href="https://supabase.com/docs/guides/getting-started/local-development#database-migrations"
+            href="https://supabase.com/docs/guides/deployment/database-migrations"
           />
         </ScaffoldSectionDetail>
         <div className="col-span-12 mt-3">

apps/www/_blog/2023-08-09-supabase-studio-3-0.mdx

@@ -134,7 +134,7 @@ Teamwork makes the dream work!
 
 We're releasing a new UI for working with database migrations right from the Studio. Database migrations give you a way to update your database using version-controlled SQL files. They describe changes that you want to make to your database, and also keep track of what changes have been made to your database over time.
 
-As migrations get run against your project from the CLI, you can see information in the Studio about when the migration was run, by who and what changes were made. [See the documentation](https://supabase.com/docs/guides/cli/local-development#database-migrations) to get started with migrations.
+As migrations get run against your project from the CLI, you can see information in the Studio about when the migration was run, by who and what changes were made. [See the documentation](https://supabase.com/docs/guides/deployment/database-migrations) to get started with migrations.
 
 <Img src="/images/blog/launch-week-8/day-3/migrations.png" alt="Migrations UI" />
 

apps/www/_blog/2024-08-12-github-copilot-extension-for-vs-code.mdx

@@ -14,7 +14,7 @@ date: '2024-08-12'
 toc_depth: 3
 ---
 
-Today we're launching a new [GitHub Copilot extension for VS Code](https://marketplace.visualstudio.com/items?itemName=Supabase.vscode-supabase-extension) to make your development with Supabase and VS Code even more delightful, starting with a Copilot-guided experience for [database migrations](/docs/guides/cli/local-development#database-migrations).
+Today we're launching a new [GitHub Copilot extension for VS Code](https://marketplace.visualstudio.com/items?itemName=Supabase.vscode-supabase-extension) to make your development with Supabase and VS Code even more delightful, starting with a Copilot-guided experience for [database migrations](/docs/guides/deployment/database-migrations).
 
 ![Database Migrations Demo](/images/blog/lw12/day-1/copilot_migration.gif)
 
@@ -32,7 +32,7 @@ The extension provides a [Chat Participant](https://code.visualstudio.com/api/ex
 
 ### Copilot-guided database migrations
 
-The extension provides a guided experience to create and apply [database migrations](/docs/guides/cli/local-development#database-migrations). Simply type `@supabase /migration <describe what you want to do>` in your Copilot Chat and the extension will generate a new SQL migration for you.
+The extension provides a guided experience to create and apply [database migrations](/docs/guides/deployment/database-migrations). Simply type `@supabase /migration <describe what you want to do>` in your Copilot Chat and the extension will generate a new SQL migration for you.
 
 ![Copilot guided database migrations demo](/images/blog/lw12/day-1/copilot_migration.gif)