3 ms·
The timeout issue was fixed in Go 1.0.3. The problem wasn't that the connections timed out, but that the database/sql package wasn't able to handle this correct
by JulienSchmidt 14y ago
The timeout issue was fixed in Go 1.0.3. The problem wasn't that the connections timed out, but that the database/sql package wasn't able to handle this correctly.
http://code.google.com/p/go/source/detail?r=b397807815a6 http://code.google.com/p/go/source/detail?r=b397807815a6
Please keep in mind, that the database/sql package is - like Go itself - still very young. There is still a lot of work to do compared to mature libraries like JDBC, but it will improve with every release.
- pico303 14y agoYeah, like the fact two queries can't run simultaneously in a single transaction. All queries in an single transaction must be run sequentially. What worries me though is that this is "by design", and seen as completely proper by the Go devs. That's the reason I stopped using Go: they have guys who don't understand databases writing their database code.