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
I wrote a database/sql driver that implements the optional ColumnConverter interface for prepared statements, and for which NumInputs() returns -1.
Technically, I wrote a databse/sqlproxy driver, for the purpose of adding hooks to DB operations, to aide in debugging. See https://gitlab.com/flimzy/errsql
But using this library with modernc.org/sqlite is what triggered the buggy behavior. modernc.org/sqlite itself does not implement the ColumnConverter interface, but it does return -1 for NumInputs. Because the proxy driver does implement ColumnConverter (because it must implement it for all drivers it proxies, or none), it triggers the observed behavior.
What did you see happen?
The default argument conversion is never called, leading to errors about invalid driver.Value values.
What did you expect to see?
I expected that the default argument conversion would happen.
The text was updated successfully, but these errors were encountered:
Go version
go version go1.22.0 linux/amd64
Output of
go env
in your module/workspace:What did you do?
I wrote a
database/sql
driver that implements the optionalColumnConverter
interface for prepared statements, and for whichNumInputs()
returns -1.Technically, I wrote a
databse/sql
proxy driver, for the purpose of adding hooks to DB operations, to aide in debugging. See https://gitlab.com/flimzy/errsqlBut using this library with
modernc.org/sqlite
is what triggered the buggy behavior.modernc.org/sqlite
itself does not implement theColumnConverter
interface, but it does return -1 forNumInputs
. Because the proxy driver does implementColumnConverter
(because it must implement it for all drivers it proxies, or none), it triggers the observed behavior.What did you see happen?
The default argument conversion is never called, leading to errors about invalid
driver.Value
values.What did you expect to see?
I expected that the default argument conversion would happen.
The text was updated successfully, but these errors were encountered: