Scanonly Select Question

[bjongbloedt]

I think I might be missing something around the scan only tag. My assumption is that this tag can be used to ignore a field on update and insert, but the field should still be added to the select statement when running a NewSelect query. Is this assumption correct?

-- More details --

As an example of what I am attempting to do, the model below is based on a table that has 3 fields. One of these fields CalculatedValue calls a function in sql to return a calculated value of some sort, meaning it cannot be updated or inserted directly. Adding scan only correctly allows inserts and updates to work w/o the field.

type Thing struct {
	bun.BaseModel   `bun:"table:Thing,alias:t"`
	ThingID         mssql.UniqueIdentifier `bun:"ThingID,pk"`
	CalculatedValue decimal.NullDecimal    `bun:"CalculatedValue,scanonly"`
	Name            string                 `bun:"Name"`
}

When I query this model using a select below, I would expect the select statement to include the CalculatedValue field, but it does not.

ctx := context.Background()
var thing Thing
err = bdb.
	NewSelect().
	Model(&thing).
	Where("ThingID = ?", "whatever").
	Scan(ctx)

From poking around a bit, the appendColumns for select here seems to use Fields, which does not include the scan only properties. This means the select query will not add the column to the raw sql, meaning no column for me. This is when I started to question if what I am doing is the intent of scan only, or if there was another path I should be looking at.

[bjongbloedt]

Ok, yeah this issue looks to be what I was looking for. Guessing this work fell of the radar when actions closed the item?