116d41a284
* feat: add changelog feature and update site navigation - Introduced a new Changelog page with pagination and detailed entry views. - Added components for displaying changelog entries, pagination, and entry details. - Updated site navigation to include a link to the new Changelog page. - Enhanced localization for changelog-related texts in marketing.json. * refactor: enhance Changelog page layout and entry display - Increased the number of changelog entries displayed per page from 2 to 20 for better visibility. - Improved the layout of the Changelog page by adjusting the container styles and removing unnecessary divs. - Updated the ChangelogEntry component to enhance the visual presentation of entries, including a new date badge with an icon. - Refined the CSS styles for Markdoc headings to improve typography and spacing. * refactor: enhance Changelog page functionality and layout - Increased the number of changelog entries displayed per page from 20 to 50 for improved user experience. - Updated ChangelogEntry component to make the highlight prop optional and refined the layout for better visual clarity. - Adjusted styles in ChangelogHeader and ChangelogPagination components for a more cohesive design. - Removed unnecessary order fields from changelog markdown files to streamline content management. * feat: enhance Changelog entry navigation and data loading - Refactored ChangelogEntry page to load previous and next entries for improved navigation. - Introduced ChangelogNavigation component to facilitate navigation between changelog entries. - Updated ChangelogDetail component to display navigation links and entry details. - Enhanced data fetching logic to retrieve all changelog entries alongside the current entry. - Added localization keys for navigation text in marketing.json. * Update package dependencies and enhance documentation layout - Upgraded various packages including @turbo/gen and turbo to version 2.6.0, and react-hook-form to version 7.66.0. - Updated lucide-react to version 0.552.0 across multiple packages. - Refactored documentation layout components for improved styling and structure. - Removed deprecated loading components and adjusted navigation elements for better user experience. - Added placeholder notes in changelog entries for clarity.
69 lines
1.8 KiB
Plaintext
69 lines
1.8 KiB
Plaintext
---
|
|
title: "Migrations"
|
|
description: "Learn how to create and manage database migrations in your application."
|
|
publishedAt: 2024-04-11
|
|
order: 1
|
|
status: "published"
|
|
---
|
|
|
|
> **Note:** This is mock/placeholder content for demonstration purposes.
|
|
|
|
Database migrations allow you to version control your database schema changes and apply them consistently across environments.
|
|
|
|
## Creating a Migration
|
|
|
|
To create a new migration, use the following command:
|
|
|
|
```bash
|
|
pnpm --filter web supabase:db:diff
|
|
```
|
|
|
|
This will generate a new migration file in the `apps/web/supabase/migrations` directory based on the differences between your local database and the schema files.
|
|
|
|
## Applying Migrations
|
|
|
|
To apply migrations to your local database:
|
|
|
|
```bash
|
|
pnpm --filter web supabase migrations up
|
|
```
|
|
|
|
## Migration Best Practices
|
|
|
|
1. **Always test migrations locally first** before applying to production
|
|
2. **Make migrations reversible** when possible by including DOWN statements
|
|
3. **Use transactions** to ensure atomic operations
|
|
4. **Add indexes** for foreign keys and frequently queried columns
|
|
5. **Include RLS policies** in the same migration as table creation
|
|
|
|
## Example Migration
|
|
|
|
```sql
|
|
-- Create a new table
|
|
CREATE TABLE tasks (
|
|
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
|
|
account_id UUID NOT NULL REFERENCES accounts(id) ON DELETE CASCADE,
|
|
title TEXT NOT NULL,
|
|
completed BOOLEAN DEFAULT false,
|
|
created_at TIMESTAMPTZ DEFAULT now()
|
|
);
|
|
|
|
-- Add RLS
|
|
ALTER TABLE tasks ENABLE ROW LEVEL SECURITY;
|
|
|
|
-- Create policies
|
|
CREATE POLICY "Users can view their account tasks"
|
|
ON tasks FOR SELECT
|
|
USING (account_id IN (SELECT get_user_accounts(auth.uid())));
|
|
```
|
|
|
|
## Resetting the Database
|
|
|
|
To completely reset your local database with the latest schema:
|
|
|
|
```bash
|
|
pnpm supabase:web:reset
|
|
```
|
|
|
|
This will drop all tables and reapply all migrations from scratch.
|