Escape column names that conflict with Rust keywords in CLI about sea-orm HOT 5 CLOSED

Good point!

from sea-orm.

Any suggestion on the naming convention? How about an underscore at the end?

from sea-orm.

I didn't make any suggestions for this because I am not sure 😄

I guess type_ with an underscore could work.. or type_col (adding _col). I'm not sure of any better options than these.

from sea-orm.

I think we can leave it for the user to decide how to resolve the name conflict.

Personally think that neither r#type nor type_ be a good option. For me, I would simply choose another name to avoid conflicting with Rust keywords.

#[derive(Clone, Debug, PartialEq, DeriveModel, DeriveActiveModel)]
pub struct Model {
    pub id: i32,
    pub type_of: String,
}

#[derive(Copy, Clone, Debug, EnumIter, DeriveCustomColumn)]
pub enum Column {
    Id,
    TypeOf,
}

impl IdenStatic for Column {
    fn as_str(&self) -> &str {
        match self {
            Self::TypeOf => "type",
            _ => self.default_as_str(),
        }
    }
}

from sea-orm.

The problem is that users will integrate existing databases with SeaORM.. and usually you don't want your framework / language to dictate your database, it should be flexible enough to avoid issues like this

from sea-orm.