tree 1ef38aa70b7bc139fb0f23153283a33e68cd2660
parent b7c3ca6c83cbdca95d734df8aa07c5ddb8ab3db0
author Knut Olav Løite <koloite@gmail.com> 1612425843 +0100
committer GitHub <noreply@github.com> 1612425843 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgG6pzCRBK7hj4Ov3rIwAAdHIIACC4Attge4hQnLzGlhMJVlzl
 jSLyNp9LkrIIzl04OJ1yDRy+cjcon8tAp+9W1xC3BYC4YjWNn1HUAZecB8aVJZzl
 hzWedervHBX7w3RAdYC39uDFgAl8LuCy/vXdTf+1mI1NNijed+rSQC6zKMrETWq7
 gNgQluK3Vw6I6uRf94IGlFt7N3tfYIJHlMMF+wlzwfCtULgcSn9zLUiTQ7aoADMF
 JlAuoETPz4OynR4I1JU1UFMcAYkqnxIbJwj6faDJw8y+ZXPcU4ySarMz/gdafmi3
 uUdqNAal26dr2ck+eykuKDo/7v+f2DhAQgVvyLu4vcuo+8Yhs9gCSwPbglyBBOU=
 =42BK
 -----END PGP SIGNATURE-----
 

fix(spanner/spannertest): support queries in ExecuteSql (#3640)

Normal queries from the Spanner client use the ExecuteStreamingSql method,
while DML statements use ExecuteSql. This distinction was also built into
spannertest where ExecuteSql would only support DML statements and required
a transaction to be specified. The session pool however uses ExecuteSql to
execute a simple `SELECT 1` query without specifying any transaction. This
would cause a nil pointer dereference.

This PR introduces support for queries in the ExecuteSql method. The current
logic assumes that the statement is a query if the transaction is a single-
use read-only transaction.

Fixes #3639