Hi noctisy!

With Lucid, relationships work with and directly read off of the model. So, if you omit the userId but define the relationship, you'll end up getting an exception.

Though I don't know the core team's exact reasoning, I'd imagine it is so the relationship can make use of the column decorator's mutations to build out the relationship columns. It could also be for compatibility with hooks as well.

For example, you might want a different naming convention in the model than in the table.

export default class Profile {
  @column({ isPrimary: true })
  declare id: number

  @column({
    columnName: 'profile_user_id', // column name in db
    serializeAs: null, // omit from serialization (maybe it is confidential)
  })
  declare userId: number

  @belongsTo(() => User)
  declare user: BelongsTo<Typeof User>
}

  

    

      Copied!