database/sql: in 1.8 fails to scan values in custom types, whose underlying types can be handled. #18839
Labels
Comments
urandom
changed the title
|
After another test on 1.7, it seems that this behavior wasn't supported there as well |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version)?go version go1.8rc3 linux/amd64
What operating system and processor architecture are you using (
go env)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/urandom/.go"
GORACE=""
GOROOT="/opt/go"
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build831291172=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
Consider the following playground: https://play.golang.org/p/5Dsys1-OJv
Using postgresl with lib/pq, the login variable l remains black
What did you expect to see?
In 1.7, the login variable is filled correctly, since Scan knows how to treat its underlying type.
What did you see instead?
The login variable stays blank, and there is no error.
The text was updated successfully, but these errors were encountered: