Issue

I'm experimenting with the Trino.Data.ADO package by plugging it into where we are running a custom Trino ADO client. It seems to be very drop-in-replace, though there's currently an issue.

We are using Dapper to run the queries, and Dapper automatically passes in a CommandBehavior of

CommandBehavior.SequentialAccess | CommandBehavior.SingleResult

This value of CommandBehavior causes TrinoCommand::ExecuteDbDataReaderAsync to throw with a NotSupportedException.

Proposed Solution

It seems the CommandBehavior should be treated as a flags type, and care must be given to parse it out that way when implementing TrinoCommand::ExecuteDbDataReaderAsync. (ADO docs reference)

Instead of a switch, the individual bits should be extracted using bitwise AND test.