Fallback for custom enum

[BeowulfR]

As far as I can see, if I have e.g.:

#[derive(Debug, Copy, Clone, PartialEq, Eq, EnumIter, DeriveActiveEnum)]
#[sea_orm(rs_type = "i32", db_type = "Integer")]
pub enum EnumType {
    None = 0,
    Xxxx = 161,
}

I cannot define that if e.g. in the db is 1 saved it should read it as None.

It would be nice if we could annotate the variant as fallback to prevent that hole db queries are failing because a single row contains an invalid value.

[Expurple]

What's the broader context where you want that behavior? In most cases, I want a loud error when data integrity is violated

[BeowulfR]

Therefore it should be optional, only present, when the field is annotated with an attribute.

I don't know what you want to hear regarding the broader context? It is just e.g. in our C++ Implementation the case for some enum columns (e.g. because something was a variant before, but no longer and you don't want to write migrations for every change, etc).

[BeowulfR]

It is also good to have a fallback if you don't want that a hole query is failing just because of a field which isn't that important and may contain an unexpected value.