Using struct names as column names in queries

[bevzzz]

bun bun everyone🥯

I've recently started using bun in a project at work in which I need to do some simple updates to several tables in the DB. The trouble is that the DB tables have inconsistent column names, like in the example below:

type EnglishBook struct {
	bun.BaseModel
	Id       int64
	Title    string `bun:"book_title"`
}

// Spanish books were added later and the creator of that table thought it appropriate to use a different column name
type SpanishBook struct {
	bun.BaseModel
	Id       int64
	Title    string `bun:"original_title"`
}

EnglishBook.Title column is called book_title, while titles for Spanish books are stored in the column original_title.
Now, imagine I wanted to update both tables and append ", Vol: 1" to the books' titles.
Currently it seems that I would have to write 2 different queries:

db.NewUpdate().Model((*EnglishBook)(nil)).Set("original_title = original_title || ', Vol: 1')").Exec(ctx)
db.NewUpdate().Model((*SpanishBook)(nil)).Set("book_title = book_title || ', Vol: 1')").Exec(ctx)

which feels somewhat unwieldy.
What I would like to do instead would be sth like this:

// Define a function that updates the column that corresponds to the struct's field `.Title`
func addVolumeToTitle(model interface{}) {
    db.NewUpdate().Model(model).Set("?Title = ?Title || ', Vol: 1')").Exec(ctx)
}

// Then simply call for both tables
addVolumeToTitle((*EnglishBook)(nil))
addVolumeToTitle((*SpanishBook)(nil))
}

I went through the placeholders section, but it seems to only have placeholders for listing all columns (?Columns) or PK columns, which doesn't really solve my issue.

Is there anything I could use to achieve that? Or should I think of a custom solution?

Update: fieldByGoName() is the method that would apparently be used to deliver such functionality. However, at the moment it is only used to parse the "join" tag on tables with many-to-many relationship and not for usual queries. Is my understanding correct? If so, do you think it would make sense to allow such Go-name syntax in queries?