None result should be None (fetchrow and fetch)

query = ...  # some SA select query
row = await conn.fetchrow(query)  # conn is SAConnection

When the underlying asyncpg connection returns None as the “empty” result, row should become None as well. Currently, row is not None but row.row is None. This would confuse the users who expect the API semantics to be same to asyncpg.

The same applies to fetch and execute which returns a RecordGenerator because it does not check None when instantiating Record objects.

Q: What’s the purpose of having seem-to-be-redundant Record and RecordGenerator classes? They look like a no-op proxy to asyncpg’s return objects.

[nhumrich]

@rbcarson Good catch. This is fixed in 0.8.2. RecordGenerator will now be falsey on an empty list.

[nhumrich]

Ya, thats valid. I’ll leave this open until I do something about it.