I insist that after we released a new version of sea-orm-macro, we bump the dependency and remove the path = from toml to ensure that our CI uses the released version.

I insist that after we released a new version of sea-orm-macro, we bump the dependency and remove the path = from toml to ensure that our CI uses the released version.

I noticed that it used path also, wasn't sure if it was a mistake or not.

This is awesome, you guys work so fast. Is there any examples of how to use this feature to rename columns?

Oh I see, didn't go with an attribute? Like:

#[derive(Copy, Clone, Debug, EnumIter, DeriveColumn)] 
 pub enum Column {
     #[sea(rename = "id")]
     Id,
      #[sea(rename = "full_name")]
     Name, 
 } 

We want to keep it simple and avoid using excessive macros loll

Though, I think we can also have fallback:

 impl IdenStatic for Column { 
     // the default impl is self.default_as_str()
     fn as_str(&self) -> &str { 
         match self { 
             Self::Id => "_id", 
             _ => self.default_as_str(), 
         } 
     } 
 } 

Ohh okay I see 😄 Serde uses a macro for renaming, but I guess the default_as_str() approach works fine too.. just a little bit more boiletplate code

SeaORM tries to avoid custom macro syntax. I think it was our principle to make things runtime-configurable.

Does the renaming also need to be implemented for DeriveModel? I'm not sure how to handle a model with fields which need to be renamed.

For example, how do we rename columns here:

Our assumption on naming model attributes & column enum variants:

• All model attributes are in snake-case and exists in column enum variants
  • Model attributes: id, name
• All column variants are in camel-case and exists in model attributes
  • Enum variants: Id, Name

So, that means if you want to rename one of the attribute / column you have to also update the other half of it.

I'm still a little confused, for the column you would rename it with DeriveCustomColumn and impl IdenStatic for Column.. but how do we rename a field on the model too? For exampe, if a field conflicts with a Rust keyword.

So basically the impl IdenStatic for Column is just for constructing SQL statement, i.e. how we refer this column in SQL statement.

Take your example in #76... we might do the followings

#[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(),
        }
    }
}

Ah perfect, it all makes sense now thank you @billy1624 ... again XD !!!