Do not send DELETE after QueryRow

[pajaks]

No description provided.

[nineinchnick]

When calling db.QueryRowContext() and scanning the result, the Scan() method calls Close() on the driver's result struct. The driver is not aware that there are no more results to read and issues an additional DELETE HTTP request. Because the query no longer exists on the server, it returns a 404 response, which is then returned to the calling code.

The driver should correctly set the internal err to io.EOF if there's no data and nextUri in the last received response.