How do I install the Sea Orm skill?

Run npx skillmds@latest add pedromneto97/sea-orm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sea Orm safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sea Orm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sea Orm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sea Orm?

pedromneto97 (@pedromneto97) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sea Orm by pedromneto97 — Agent Skill

Name: Sea Orm
Author: pedromneto97

Sea Orm

SeaORM v2 (open-source, Postgres/MySQL/SQLite) and SeaORM-X (commercial MSSQL) patterns for Rust backends. Use when: adding SeaORM to a project, writing migrations, generating entities, performing CRUD (insert, select, update, delete), paginating results, loading relations, handling on-conflict, using the v2 `#[sea_orm::model]` macro, COLUMN constants, find_by_*, Entity Loader, or MSSQL OUTPUT/IDENTITY_INSERT/savepoint features.

pedromneto97 9e16ede 11 files · 33.6 KB Updated Sep 17, 2026

File contents

SeaORM v2 — Skill Index

Covers sea-orm 2.0.0-rc (open-source) and SeaORM-X (MSSQL commercial). Load only the reference file(s) relevant to the task. Do not load all files at once.

Reference files

Topic	File
`Cargo.toml` dependencies, feature flags, workspace setup	`reference/01-cargo-setup.md`
`Database::connect`, `ConnectOptions`, pool, ping	`reference/02-connection.md`
Migrations — CLI, file layout, `MigratorTrait`, DDL helpers, raw SQL, seed data	`reference/03-migrations.md`
Entity structure — dense vs compact, attributes, CLI codegen, Rust↔DB type map	`reference/04-entity-structure.md`
CRUD Insert — insert one/many, `exec_with_returning`, on-conflict, IDENTITY_INSERT	`reference/05-crud-insert.md`
CRUD Select — find, filter, COLUMN constants, relations, pagination, partial model	`reference/06-crud-select.md`
CRUD Update & Delete — update one/many, delete one/many, `exec_with_returning`	`reference/07-crud-update-delete.md`
MSSQL-specific — savepoints, IDENTITY_INSERT, OUTPUT, schema rewrite, tuple IN	`reference/08-mssql-features.md`
v1 → v2 breaking changes	`reference/09-v1-v2-migration.md`
Repository boundary patterns — mappers, transactions, infra→domain error mapping	`reference/10-repository-patterns.md`

Quick decision guide

Starting a new project? → load 01-cargo-setup.md + 02-connection.md + 03-migrations.md
Defining entities? → load 04-entity-structure.md
Writing queries? → load the relevant CRUD file(s): 05, 06, or 07
Implementing repositories? → load 10-repository-patterns.md (+ relevant CRUD file)
Using MSSQL / SeaORM-X? → always also load 08-mssql-features.md
Upgrading from v1? → load 09-v1-v2-migration.md

Key v2 concepts (quick reference)

Use #[sea_orm::model] (dense format) to unlock COLUMN constants, auto find_by_*/delete_by_*, ModelEx, and Entity Loader.
exec_with_returning is supported on INSERT, UPDATE, and DELETE for Postgres, SQLite, and MSSQL.
M-N load_many no longer requires a junction entity in v2.
MSSQL IDENTITY_INSERT is handled automatically by SeaORM-X when a PK column is Set(...).
currentSchema in the MSSQL connection string auto-prefixes all queries — no explicit schema annotations needed.

---name: sea-ormdescription: SeaORM v2 (open-source, Postgres/MySQL/SQLite) and SeaORM-X (commercial MSSQL) patterns for Rust backends. Use when: adding SeaORM to a project, writing migrations, generating entities, performing CRUD (insert, select, update, delete), paginating results, loading relations, handling on-conflict, using the v2 `#[sea_orm::model]` macro, COLUMN constants, find_by_*, Entity Loader, or MSSQL OUTPUT/IDENTITY_INSERT/savepoint features.---# SeaORM v2 — Skill Index> Covers **sea-orm 2.0.0-rc** (open-source) and **SeaORM-X** (MSSQL commercial).> Load only the reference file(s) relevant to the task. Do **not** load all files at once.## Reference files| Topic | File ||-------|------|| `Cargo.toml` dependencies, feature flags, workspace setup | `reference/01-cargo-setup.md` || `Database::connect`, `ConnectOptions`, pool, ping | `reference/02-connection.md` || Migrations — CLI, file layout, `MigratorTrait`, DDL helpers, raw SQL, seed data | `reference/03-migrations.md` || Entity structure — dense vs compact, attributes, CLI codegen, Rust↔DB type map | `reference/04-entity-structure.md` || CRUD Insert — insert one/many, `exec_with_returning`, on-conflict, IDENTITY_INSERT | `reference/05-crud-insert.md` || CRUD Select — find, filter, COLUMN constants, relations, pagination, partial model | `reference/06-crud-select.md` || CRUD Update & Delete — update one/many, delete one/many, `exec_with_returning` | `reference/07-crud-update-delete.md` || MSSQL-specific — savepoints, IDENTITY_INSERT, OUTPUT, schema rewrite, tuple IN | `reference/08-mssql-features.md` || v1 → v2 breaking changes | `reference/09-v1-v2-migration.md` || Repository boundary patterns — mappers, transactions, infra→domain error mapping | `reference/10-repository-patterns.md` |## Quick decision guide- **Starting a new project?** → load `01-cargo-setup.md` + `02-connection.md` + `03-migrations.md`- **Defining entities?** → load `04-entity-structure.md`- **Writing queries?** → load the relevant CRUD file(s): `05`, `06`, or `07`- **Implementing repositories?** → load `10-repository-patterns.md` (+ relevant CRUD file)- **Using MSSQL / SeaORM-X?** → always also load `08-mssql-features.md`- **Upgrading from v1?** → load `09-v1-v2-migration.md`## Key v2 concepts (quick reference)- Use `#[sea_orm::model]` (dense format) to unlock `COLUMN` constants, auto `find_by_*`/`delete_by_*`, `ModelEx`, and Entity Loader.- `exec_with_returning` is supported on INSERT, UPDATE, and DELETE for Postgres, SQLite, and MSSQL.- M-N `load_many` no longer requires a junction entity in v2.- MSSQL `IDENTITY_INSERT` is handled automatically by SeaORM-X when a PK column is `Set(...)`.- `currentSchema` in the MSSQL connection string auto-prefixes all queries — no explicit schema annotations needed.

Frequently asked questions