https://issues.apache.org/bugzilla/show_bug.cgi?id=56586
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> --- Honestly, I'm surprised that "SET search_path [..]" will be affected by a rollback. I know it's no basis for comparison, but MySQL does not appear to behave this way: mysql> begin; Query OK, 0 rows affected (0.01 sec) mysql> set @foo := 'bar'; Query OK, 0 rows affected (0.00 sec) mysql> select @foo; +------+ | @foo | +------+ | bar | +------+ 1 row in set (0.00 sec) mysql> rollback; Query OK, 0 rows affected (0.00 sec) mysql> select @foo; +------+ | @foo | +------+ | bar | +------+ 1 row in set (0.00 sec) I think this should be an /option/ that defaults to false because it will execute another query (COMMIT) on the server side. If most clients do not need it, there's no need to execute a COMMIT unless the application absolutely needs it. Any objections to an option rather than strict behavior? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
