Open zachkinstner opened 11 years ago
Since RexConnectConsole
operates at the Command level, this feature only applies to RexConnectServer
.
Perhaps some of the example options above would be better-suited as Config settings. This would allow the console to use them. It would also allows the server to, for example, increase the timeout for a particular command within a request.
Possible option: auto-commit an individual query within a session. RexPro provides a transaction
parameter, which specifies whether a query should be wrapped in a transaction. It's not clear to me right now if:
g
variable gets overwritten, and the session becomes corruptedOption (A) is ideal, but it seems that (B) or (C) are more likely cases. In any case, I can't really think of a good use case for this right now.
Introduce an options collection at the request level. Some interesting options might be:
Probable request structure:
Unknown options keys and invalid option values would return a request-level error.