Prepared stament with RETURNING value about npgsql HOT 2 CLOSED

To be honest, I had doubts to use ExecuteScalarAsync to catch the returning value but when I check msdoc equivalent(doc) of this command. It is exactly for my specific use case and I think there is no problem with using that. Therefore, I cleared my doubts but this ticket can still stay to answer why we cannot use named parameter with out direction in prepared statements or can be closed if it is not necessary.

from npgsql.

@onurmx an output parameter generally isn't the right thing for executing a SQL with RETURNING - there's no function/procedure being callled, just a plain regular SQL statement returning the generated columns as a normal resultset (as if you ran a SELECT). So you can simply omit the parameter with ParameterDirection.Output, and use ExecuteReaderAsync (or ExecuteScalarAsync).

from npgsql.