@a631807682 here's the new PR with the final solution. Appreciate all the info and time you've provided on this! 🚀 🎉

@a631807682 am I correct in assuming @jinzhu will be merging into master, after reviewing? or would that be you as well?

I usually wait for at least 2 members to review, and jinzhu will review all PRs and merge them when he is free.

OMG, I've been treating this as a feature the whole time.

It doesn't seem like a "Non breaking API changes". Is this the expected behavior of this function itself?

I'm not sure if this is related, but there's a significant change in the Scan function's behaviour. The GORM version just got a minor update, but now Scan wipes clean the whole struct. That's a pretty big change.

We used to use Scan something like this:

type SomeStruct struct {
    Name        string
    Date        null.Time
    Description string
    ID          uint64
}

data := SomeStruct{
    ID:   1,
    Date: null.TimeFrom(time.Now()),
}

db.Table("some_table").
    Select("name, description").
    Where("id = ?", data.ID).
    Scan(&data)

The intention was to fill in new data while keeping the already populated fields intact.
But now, after the update, the struct is wiped clean and only the selected data is present after Scan.
That seems like a major behavioural change.