[Blog] Edit

Author: tyt2y3

Blog/blog/2025-10-20-sea-orm-2.0.md

@@ -354,7 +354,7 @@ pub enum Relation {
 }
 ```
 
-This aspect is not different from 1.0. A `Related` impl will not be generated. The relation can be used in joins, but currently not supported by the loader (we do plan to support it soon).
+This aspect is not so different from 1.0. A `Related` impl will not be generated, but the relation can still be used in loader.
 
 ### Composite foreign key
 

Blog/blog/2025-10-30-sea-orm-2.0.md

@@ -25,7 +25,7 @@ SeaORM used to adopt a schema‑first approach: meaning you design database tabl
 
 Entity‑first flips the flow: you hand-write the entity files, and let SeaORM generates the tables and foreign keys for you.
 
-All you have to do is to add the following to your `main.rs` right after creating the database connection:
+All you have to do is to add the following to your [`main.rs`](https://github.com/SeaQL/sea-orm/blob/master/examples/quickstart/src/main.rs) right after creating the database connection:
 
 ```rust
 let db = &Database::connect(db_url).await?;
@@ -37,7 +37,9 @@ This requires two feature flags `schema-sync` and `entity-registry`, and we're g
 
 ## Unfolding
 
-The above function `get_schema_registry` desugars into the following:
+### Entity Registry
+
+The above function `get_schema_registry` unfolds into the following:
 
 ```rust
 db.get_schema_builder()
@@ -53,7 +55,7 @@ You might be wondering: how can SeaORM recognize my entities when, at compile ti
 
 Rest assured, there's no source‑file scanning or other hacks involved - this is powered by the brilliant [`inventory`](https://docs.rs/inventory/latest/inventory/) crate. The `inventory` crate works by registering items (called plugins) into linker-collected sections.
 
-At compile-time, each `Entity` module registers itself to the global `inventory` along with their module paths and some metadata. On runtime, SeaORM then filters the Entities you requested and construct a `SchemaBuilder`.
+At compile-time, each `Entity` module registers itself to the global `inventory` along with their module paths and some metadata. On runtime, SeaORM then filters the Entities you requested and construct a [`SchemaBuilder`](https://docs.rs/sea-orm/2.0.0-rc.15/sea_orm/schema/struct.SchemaBuilder.html).
 
 The `EntityRegistry` is completely optional and just adds extra convenience, it's perfectly fine for you to `register` Entities manually like above.
 
@@ -73,13 +75,14 @@ Let's walk through the different scenarios:
 
 Let's say you added a new Entity under `mod.rs`
 
-```rust
+```rust title="entity/mod.rs"
 //! `SeaORM` Entity, @generated by sea-orm-codegen 2.0.0-rc.14
 
 pub mod prelude;
 
 pub mod post;
 pub mod upvote; // ⬅ new entity module
+..
 ```
 
 The next time you `cargo run`, you'll see the following:
@@ -92,22 +95,21 @@ This will create the table along with any foreign keys.
 
 ### Adding Columns
 
-```rust
-mod profile {
-    use sea_orm::entity::prelude::*;
-
-    #[sea_orm::model]
-    #[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
-    #[sea_orm(table_name = "profile")]
-    pub struct Model {
-        #[sea_orm(primary_key)]
-        pub id: i32,
-        pub picture: String,
-        pub date_of_birth: Option<DateTimeUtc>, // ⬅ new column
-    }
-
-    impl ActiveModelBehavior for ActiveModel {}
+```rust title="entity/profile.rs"
+use sea_orm::entity::prelude::*;
+
+#[sea_orm::model]
+#[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
+#[sea_orm(table_name = "profile")]
+pub struct Model {
+    #[sea_orm(primary_key)]
+    pub id: i32,
+    pub picture: String,
+    pub date_of_birth: Option<DateTimeUtc>, // ⬅ new column
+    ..
 }
+
+impl ActiveModelBehavior for ActiveModel {}
 ```
 
 The next time you `cargo run`, you'll see the following:
@@ -161,27 +163,27 @@ Nice, isn't it?
 
 ### Add Foreign Key
 
-Let's say we create a new table with a foreign key:
+Let's create a new table with a foreign key:
 
-```rust
-mod upvote {
-    use sea_orm::entity::prelude::*;
-
-    #[sea_orm::model]
-    #[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
-    #[sea_orm(table_name = "upvote")]
-    pub struct Model {
-        #[sea_orm(primary_key, auto_increment = false)]
-        pub post_id: i32,
-        #[sea_orm(belongs_to, from = "post_id", to = "id")]
-        pub post: HasOne<super::post::Entity>,
-        ..
-    }
-
-    impl ActiveModelBehavior for ActiveModel {}
+```rust title="entity/upvote.rs"
+use sea_orm::entity::prelude::*;
+
+#[sea_orm::model]
+#[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
+#[sea_orm(table_name = "upvote")]
+pub struct Model {
+    #[sea_orm(primary_key, auto_increment = false)]
+    pub post_id: i32,
+    #[sea_orm(belongs_to, from = "post_id", to = "id")]
+    pub post: HasOne<super::post::Entity>,
+    ..
 }
+
+impl ActiveModelBehavior for ActiveModel {}
 ```
 
+The next time you `cargo run`, you'll see the following:
+
 ```sh
 CREATE TABLE "upvote" (
     "post_id" integer NOT NULL PRIMARY KEY,
@@ -196,22 +198,20 @@ If however, the `post` relation is added after the table has been created, then
 
 Now, let's say we've forgotten to add a unique constraint on user name:
 
-```rust
-mod user {
-    use sea_orm::entity::prelude::*;
-
-    #[sea_orm::model]
-    #[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
-    #[sea_orm(table_name = "user")]
-    pub struct Model {
-        #[sea_orm(primary_key)]
-        pub id: i32,
-        #[sea_orm(unique)] // ⬅ add unique key
-        pub name: String,
-        #[sea_orm(unique)]
-        pub email: String,
-        ..
-    }
+```rust title="entity/user.rs"
+use sea_orm::entity::prelude::*;
+
+#[sea_orm::model]
+#[derive(Clone, Debug, PartialEq, Eq, DeriveEntityModel)]
+#[sea_orm(table_name = "user")]
+pub struct Model {
+    #[sea_orm(primary_key)]
+    pub id: i32,
+    #[sea_orm(unique)] // ⬅ add unique key
+    pub name: String,
+    #[sea_orm(unique)]
+    pub email: String,
+    ..
 }
 ```
 
@@ -221,7 +221,7 @@ The next time you `cargo run`, you'll see the following:
 CREATE UNIQUE INDEX "idx-user-name" ON "user" ("name")
 ```
 
-As mentioned in the previous blog post, you'll also get a shorthand method generated on the Entity for free:
+As mentioned in the previous blog post, you'll also get a shorthand method generated on the Entity:
 
 ```rust
 user::Entity::find_by_name("Bob")..
@@ -253,11 +253,11 @@ DROP INDEX "idx-user-name"
 
 Note that in general schema sync would not attempt to do any destructive actions, so meaning no `DROP` on tables, columns and foreign keys. Dropping index is an exception here.
 
-Every time the application starts, a full schema discovery is performed. It's not recommended to enable this in production, and so this is gated behind a feature flag `schema-sync` that can be turned off based on build profile.
+Every time the application starts, a full schema discovery is performed. This may not be desirable in production, so `sync` is gated behind a feature flag `schema-sync` that can be turned off based on build profile.
 
 ## 🧭 Instant GraphQL API
 
-With [Seaography](https://github.com/SeaQL/seaography), the Entities you wrote can instantly be exposed as a GraphQL schema, with full CRUD, filtering and pagination. The GraphQL data loader is actually more powerful, as it allows nesting relations with arbitrary complexity.
+With [Seaography](https://github.com/SeaQL/seaography), the Entities you wrote can *instantly* be exposed as a GraphQL schema, with full CRUD, filtering and pagination. No extra macros, no Entity re-generation is needed!
 
 With SeaORM and Seaography, you can prototype quickly and stay in the flow. And because Seaography is highly customizable, you can gradually shift resolver logic into your own implementation as the application evolves, and layer access control on top before the project goes to production.
 
@@ -296,7 +296,7 @@ type User {
 }
 ```
 
-## 🖥️ SeaORM Pro: Professional Admin Panel
+## 🖥️ SeaORM Pro: Admin Panel
 
 <img src="/blog/img/sea-orm-pro-light.png#light" />
 <img src="/blog/img/sea-orm-pro-dark.png#dark" />