Re:Practical Persistence in Go: SQL Databases
by rakoo on Thursday June 18, 2015 @10:56AM
(#9738901)
> http.Error(w, err.Error(), 500)
This will send the sql error directly to the client. I don't think it's a good idea because it can leak important information to it; it's better to log this error on the server and send back a generic failure message to the client.
This will send the sql error directly to the client. I don't think it's a good idea because it can leak important information to it; it's better to log this error on the server and send back a generic failure message to the client.