You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is actually deeper: the code does not do what its comments describe, on both NULL values, empty strings and empty byte slices. The comments say "if an empty UUID comes from a table, we return a null UUID", but actually what happens is:
Scan returns a nil error (not a null UUID)
Scan leaves the receiver unchanged instead of setting it to uuid.Nil as return a null UUID should probably be interpreted
Release 1.3.0 introduced the uuid.Valid field partly for such cases, but that field is not actually used. Maybe the changes to sql.go which used that new feature were not committed when building the release ?
The text was updated successfully, but these errors were encountered: