Use ActiveEnum field as composite primary key

[billy1624]

PR Info

• Closes Composite primary key with enum causes generated entity to fail to compile #1364

Breaking Changes

• Provided a blanket implementation of TryFromU64 for all ActiveEnum

impl<T> TryFromU64 for T
where
    T: ActiveEnum,
{
    fn try_from_u64(_: u64) -> Result<Self, DbErr> {
        Err(DbErr::ConvertFromU64(
            "Fail to construct ActiveEnum from a u64, if your primary key consist of a ActiveEnum field, its auto increment should be set to false."
        ))
    }
}

[tyt2y3]

I don't understand the intention of this bit, and I think it SHOULD fail to insert instead of passing

[billy1624]

It does an update instead of insert.

// The `..model.into_active_model()` expands into

let _ = ActiveModel {
        category: Set(Some(Category::Big)),
        color: Set(Some(Color::Black)),
        id: Unchanged( ... )
    }
    .save(db)
    .await?;

[tyt2y3]

Oh Right

[tyt2y3]

Can we also add an insert conflict test case

[billy1624]

We can insert a row with duplicate ID. But I cannot assert the exact error, since it's database dependent. 66cffd4

[tyt2y3]

Yes, is_err would do

[billy1624]

Alright, good to go

[tyt2y3]

Cool