ydb-go-sdk
ydb-go-sdk copied to clipboard
feat: standardization/unification for Query
Feature Request
I want to write a wrapper package that uses Execute/ReadRow/ReadResultSet from Session and TxActor, encountered that the signature of the methods became very different
optionspackage is imported frominternal, so I cannot describe a partial interface consisting of 1 method.- for
Session&TxActoroptions have become different – ExecuteOption & TxExecuteOption, which prevents you from using 1 interface for them - I don't like the fact that the
Executecall inSessiongivesTransaction, because of this method signature is different fromTxActor, which does not allow to use 1 interface, as I used to do withdatabase/sql. That said, I understand the idea of needing to returnTransaction, but maybe inTxActor, it should also be returned?