sqldb-logger
sqldb-logger copied to clipboard
simukti
A logger for Go SQL database driver without modifying existing *sql.DB stdlib usage.
It's hard to recognize which actions is has a level between [queryer, executer, preparer]. DB 'action' messages are needed to collect in a file. Also, log levels are separated by...
Hi, I'm trying to use this to wrap a driver that doesn't implement the context-aware methods from the sql package, but when I call `db.Prepare` I get `driver.ErrSkip`. That's because...
Hi, I'm trying to use this together with sqlx and have discovered a weird issue - when trying to insert uint64 value I get a: `error: sql: converting argument $1...
I wanted the ability to inject some additional log fields at init time. Building on `Option` seemed like a logic fit for this functionality, which I've called "additional fields". This...
Fixes #60 https://github.com/golang/go/blob/0e85fd7561de869add933801c531bf25dee9561c/src/database/sql/convert.go#L129 NamedValueChecker can also be implemented on connection, and above (golang's sql package) code fallbacks to it when statement does not implement it. This PR implements same behavior.
Great work on this library! It's really useful for debugging 👍🏼 I'm wondering if [these log levels](https://github.com/simukti/sqldb-logger/blob/c462204a331714d7e6c0c43020a31e6bbf3f5ffc/transaction.go#L25) can be made configurable instead of being hard-coded to Debug level.
my code like this ```golang db, err := sqlx.Connect("mysql", dbURL) if err != nil { //todo handle error } var writers []io.Writer writers = append(writers, zerolog.ConsoleWriter{Out: os.Stderr}) mw := io.MultiWriter(writers...)...
