Re: [go-nuts] database/sql doesn't return error for query-string-destination if NULL bug or feature

2020-09-12 Thread Stephan Lukits
On 9/12/20 8:25 AM, Tamás Gulácsi wrote: database/sql.DB is a pool. If you don't want to close it, SetMaxIdleConns(1), or better, use a db.Conn(). Thanks for the hint. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

Re: [go-nuts] database/sql doesn't return error for query-string-destination if NULL bug or feature

2020-09-11 Thread Tamás Gulácsi
database/sql.DB is a pool. If you don't want to close it, SetMaxIdleConns(1), or better, use a db.Conn(). stephan...@gmail.com a következőt írta (2020. szeptember 11., péntek, 21:02:26 UTC+2): > On Friday, 11 September 2020 at 21:04:11 UTC+3 mar...@gmail.com wrote: > >> Which sqlite driver are

Re: [go-nuts] database/sql doesn't return error for query-string-destination if NULL bug or feature

2020-09-11 Thread Stephan Lukits
On Friday, 11 September 2020 at 21:04:11 UTC+3 mar...@gmail.com wrote: > Which sqlite driver are you using? That sounds like a bug. > "github.com/mattn/go-sqlite3" > > On Fri, Sep 11, 2020 at 10:56 AM Stephan Lukits wrote: > >> I passed a string-type pointer (as last destination) to a

Re: [go-nuts] database/sql doesn't return error for query-string-destination if NULL bug or feature

2020-09-11 Thread Marcin Romaszewicz
Which sqlite driver are you using? That sounds like a bug. On Fri, Sep 11, 2020 at 10:56 AM Stephan Lukits wrote: > I passed a string-type pointer (as last destination) to a sql.DB.Query > call which had a NULL value as field value. No error was returned and all > other fields got the

[go-nuts] database/sql doesn't return error for query-string-destination if NULL bug or feature

2020-09-11 Thread Stephan Lukits
I passed a string-type pointer (as last destination) to a sql.DB.Query call which had a NULL value as field value. No error was returned and all other fields got the appropriate values but the connection was silently closed. I noticed because it was an in-memory (sqlite3) database which all of