-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: standardization/unification for Query #1265
Comments
Some options for query session Execute not aplliable to transaction Execute |
What's the answer to that question?
|
In Table service I made some design issues, which I tried to fix in Query service |
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
options
package is imported frominternal
, so I cannot describe a partial interface consisting of 1 method.Session
&TxActor
options have become different – ExecuteOption & TxExecuteOption, which prevents you from using 1 interface for themExecute
call inSession
givesTransaction
, 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?The text was updated successfully, but these errors were encountered: