tauri-app-sql

When to use this skill

• Using SQLite, MySQL, or PostgreSQL in Tauri
• SQL migrations or connection configuration
• Secure frontend query access

• "sql", "sqlite", "postgres", "mysql", "migration"
• "database", "migration", "connection configuration", "SQL"

How to use this skill

1. Select the database engine and connection string
2. Configure migrations in tauri.conf.json
3. Enable SQL plugin capabilities with scoped access
4. Validate queries and error handling in the app flow

Outputs

• Database integration plan
• Minimal-permission capability checklist

Scope

• Boundary: SQL plugin configuration and usage only
• Key points: Migrations setup and capability scoping

References

• https://v2.tauri.app/llms.txt
• https://v2.tauri.app/plugin/sql/
• https://v2.tauri.app/zh-cn/plugin/sql/

Keywords

Gotchas

1. Version Compatibility: Pay attention to compatibility between framework versions and dependent libraries; APIs may differ across versions
2. Configuration File Format: Incorrect configuration file format is the most common issue; it is recommended to use the editor's syntax checking
3. Environment Variables: Ensure all necessary environment variables are set correctly; do not hardcode sensitive information
4. Dependency Conflicts: Pay attention to dependency conflicts when multiple versions coexist; use lock files to lock versions
5. Performance Pitfalls: Pay attention to performance optimization in large data volume scenarios; avoid common issues such as N+1 queries

Usage Flow

Step 1: Environment Preparation

Step 2: Configuration Initialization

Step 3: Core Function Usage

Step 4: Testing and Verification

Step 5: Deployment and Launch