logSQL() messing up console if there is binary BLOB param

[afriza]

The logSQL() function caused problem in the console when I inserted binary BLOB and ExecLogFunc is set to print the SQL.

dbx/query.go

Lines 109 to 110 in cecf5a8

	} else if bs, ok := v.([]byte); ok {
	sv = "'" + strings.Replace(string(bs), "'", "''", -1) + "'"

For now, in ExecLogFunc I check using string matching if the SQL is involving binary BLOB and don't print it to console.

[ganigeorgiev]

I've updated the default logger in v1.9 to print the raw bytes as hex since that is how most db tools (including sqlite3 with mode .quote) seems to handle it.

[afriza]

Thank you.

Even better, maybe in future, if there's a max limit..

I saw some go logs showing initial & last few number of bytes as hex.. and the middle shows something like [... 5678 bytes of data ... ]