Use pointer Valuer to fix nil pointer issue

[blockloop]

type Opportunity struct {
    ID                  *int       `db:"OpportunityId,omitempty"`
    GlobalOpportunityID *uuid.UUID `db:"GlobalOpportunityId,omitempty"`
}

I am using a this struct and when I call database actions I'm running into golang/go#8415 because go is calling Value() even though the pointer is nil. This is something they appear to be fixing in a later version, but their suggestion is to put a Valuer on *UUID instead of UUID. I changed the sql.go Value() method in my vendor folder to use a pointer and the issue went away.

Does this create any problems that I'm missing?

[blockloop]

Scratch this. By creating the Value() method for *UUID you can no longer use UUID without a pointer.