OR condition relation SeaQL/sea-orm#1433

Author: darkmmon

SeaORM/docs/0.12.x-CHANGELOG_temp.md

@@ -43,7 +43,6 @@ impl MigratorTrait for Migrator {
     }
 }
 ```
-================================ All Changes above was being Documented ================================
 * Added option to construct chained AND / OR join on condition https://github.com/SeaQL/sea-orm/pull/1433
 ```rs
 use sea_orm::entity::prelude::*;
@@ -110,6 +109,7 @@ assert_eq!(
     .join(" ")
 );
 ```
+================================ All Changes above was being Documented ================================
 * Supports entity with composite primary key of length 12 https://github.com/SeaQL/sea-orm/pull/1508
     * Implemented `IntoIdentity` for `Identity` https://github.com/SeaQL/sea-orm/pull/1508
     * `Identity` supports up to identity tuple of `DynIden` with length up to 12 https://github.com/SeaQL/sea-orm/pull/1508

SeaORM/docs/06-relation/06-custom-join-condition.md

@@ -17,6 +17,7 @@ It can be done via one of the following ways.
 ## Relation
 
 Add your additional join conditions directly to the relation enum. The easiest way is to provide a `sea_query::SimpleExpr` via `on_condition` procedural macros attribute.
+If you want to have a `OR` condition relation, you can use `condition_type = "any"` to alter the relation.
 
 ```rust
 #[derive(Copy, Clone, Debug, EnumIter, DeriveRelation)]
@@ -29,6 +30,13 @@ pub enum Relation {
         on_condition = r#"super::fruit::Column::Name.like("%tropical%")"#
     )]
     TropicalFruit,
+    // specify `condition_type = "any"` to override it
+    #[sea_orm(
+        has_many = "super::fruit::Entity",
+        on_condition = r#"super::fruit::Column::Name.like("%tropical%")"#
+        condition_type = "any",
+    )]
+    OrTropicalFruit,
 }
 ```
 
@@ -127,6 +135,7 @@ assert_eq!(
 ## Custom Join
 
 Last but not least, custom join conditions can be defined at the point you construct the join expression.
+Overriding condition relation can also be done in custom join on the fly.
 
 ```rust
 assert_eq!(
@@ -153,6 +162,19 @@ assert_eq!(
                         .into_condition()
                 })
         )
+        .join_as_rev(
+            JoinType::LeftJoin,
+            cake_filling::Relation::Cake
+                .def()
+                // chained AND / OR join on condition
+                .condition_type(ConditionType::Any)
+                .on_condition(|left, _right| {
+                    Expr::col((left, cake_filling::Column::CakeId))
+                        .gt(10)
+                        .into_condition()
+                }),
+            Alias::new("cake_filling_alias")
+        )
         .join(JoinType::LeftJoin, filling::Relation::Vendor.def())
         .build(DbBackend::MySql)
         .to_string(),
@@ -161,6 +183,7 @@ assert_eq!(
         "LEFT JOIN `fruit` ON `cake`.`id` = `fruit`.`cake_id` AND `fruit`.`name` LIKE '%tropical%'",
         "LEFT JOIN `cake_filling` ON `cake`.`id` = `cake_filling`.`cake_id` AND `cake_filling`.`cake_id` > 10",
         "LEFT JOIN `filling` ON `cake_filling`.`filling_id` = `filling`.`id` AND `filling`.`name` LIKE '%lemon%'",
+        "LEFT JOIN `cake_filling` AS `cake_filling_alias` ON `cake_filling_alias`.`cake_id` = `cake`.`id` OR `cake_filling_alias`.`cake_id` > 10",
         "LEFT JOIN `vendor` ON `filling`.`vendor_id` = `vendor`.`id`",
     ]
     .join(" ")