Migrate SeaORM 1.0 entities and queries to SeaORM 2.0 patterns.
npx skills add https://github.com/FlyinPancake/yoink --skill sea-orm-2-flyinpancake
Please help me install this Agent Skill. Skill: sea-orm-2 Source: https://github.com/FlyinPancake/yoink/tree/main/.agents/skills/sea-orm-2 Command: npx skills add https://github.com/FlyinPancake/yoink --skill sea-orm-2-flyinpancake
SeaORM 2.0 introduces breaking API and workflow changes compared to SeaORM 1.0, and the most common mistakes come from carrying old assumptions (entity structure, column typing, query composition, and eager-loading patterns) into new code.
Model using #[sea_orm::model] and relation attributes like has_one, has_many, belongs_to, self_ref.Entity::COLUMN for compile-time type safety and safer filters/expressions instead of the older untyped Column API.insert vs save semantics to avoid unexpected writes.Entity::load() API and .with(...) to avoid N+1 queries through joins/data-loader behavior.ExprTrait), and platform-specific gotchas (PostgreSQL identity/serial, SQLite integer mapping).Ask the skill to explain how to migrate one of your existing SeaORM 1.0 entities and queries to SeaORM 2.0, including the updated entity definition, strongly-typed column usage, and the correct eager-loading approach for your relations.
High-intent search queries and answers about installing and using this skill.
SeaORM 2.0 introduces breaking API changes, requiring updates to entity structure, column typing, query composition, and relational eager-loading patterns to resolve compilation issues from outdated 1.0 assumptions.
SeaORM 2.0 eager loading uses the Entity::load() API with .with(...) to fetch relations efficiently, preventing N+1 queries through underlying join and data-loader behavior instead of older untyped patterns.
SeaORM 2.0 typed columns use Entity::COLUMN for compile-time type safety when building filters and expressions, replacing the older untyped Column API to ensure safer query composition.
SeaORM 2.0 ActiveModel handles nested inserts and updates via a builder pattern, requiring careful attention to insert versus save semantics to prevent unexpected database writes during persistence.
Common SeaORM 2.0 migration anti-patterns include missing required imports like ExprTrait and ignoring platform-specific gotchas like PostgreSQL identity/serial mapping and SQLite integer mapping differences.
Yes, SeaORM 2.0 requires updating query composition for Rust CRUD operations, as typed expressions and Entity::load patterns replace older untyped APIs to enforce compile-time safety.
elcoospExplains SeaORM 2.0 patterns including Entity Loader and nested ActiveModel.
ngxtmProvide asynchronous ORM operations with compile-time checked SQL queries for Rust.
actionbookGenerate domain-constrained architecture plans for Rust HTTP servers.
ngxtmFacilitate type-safe database interactions in Rust applications using Diesel ORM.