Handling Errors

Almost all operations with database/sql types return an error as the last value. You should always check these errors, never ignore them. There are a few places where error behavior is special-case, or there’s something additional you might need to know. Errors From Iterating Resultsets Consider the following code: for rows.Next() { // ... } if err = rows.Err(); err != nil { // handle the error he

[igtm]

“if driverErr, ok := err.(*mysql.MySQLError); ok { if driverErr.Number == mysqlerr.ER_ACCESS_DENIED_ERROR { // Handle the permission-denied error } }”