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
whenever you try to execute an invalid statement in a transaction an error isn't returned (nor a panic thrown) the program just hangs.
I'd initially noticed this when inserting twice into a table that expected a column to be unique assuming I'd see an error but instead the program just hung.
this does not seem to be directly related to the unique constraint, it seems to happened with any invalid statement; even if they aren't valid SQL.
strangely enough: removing defer db.Close() removes the hang and allows transaction.Exec to panic (although, I'd expect an error to be returned, not a panic).
seems this is something to do with the pool being unable to close after an invalid statement?
Hi,
whenever you try to execute an invalid statement in a transaction an error isn't returned (nor a
panic
thrown) the program just hangs.I'd initially noticed this when inserting twice into a table that expected a column to be unique assuming I'd see an error but instead the program just hung.
this does not seem to be directly related to the unique constraint, it seems to happened with any invalid statement; even if they aren't valid SQL.
here's a example:
running this program yields the following then hangs forever:
The text was updated successfully, but these errors were encountered: