Kure

In theory, this issues is fix in v3.0.1, but I still met ``` runtime error: index out of range [7] with length 0 runtime/debug.Stack() /home/xx/Apps/go/src/runtime/debug/stack.go:24 +0x65 golang.org/x/sync/singleflight.newPanicError({0x120c9a0, 0xc26e4c02d0}) /home/xx/.go/pkg/mod/golang.org/x/[email protected]/singleflight/singleflight.go:35 +0x2c...

`ErrorOutputPaths`用于设置zap的内部错误输出而不是logger的error输出，如果你要实现error和info输出的分离，应该通过`zapcore.NewTee`设置多个输出并结合`LevelEnabler`来实现。具体可参照[Example (AdvancedConfiguration)](https://godoc.org/go.uber.org/zap#example-package--AdvancedConfiguration)

根本原因是mysql驱动从1.7.0增加了unsigned int类型的返回 > return unsigned in database type name when necessary (https://github.com/go-sql-driver/mysql/pull/1238) 考虑修改 https://github.com/GoAdminGroup/go-admin/blob/master/modules/db/converter.go#L12C6-L12C19 的SetColVarType，将所有unsigned int都用int64去scan才能解决根本问题