DO NOT REPLY [Bug 42018] - JDBC Sampler always commits

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42018>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42018





------- Additional Comments From sebb@apache.org  2007-04-30 15:37 -------
(In reply to comment #3)
> Created an attachment (id=20036)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20036&action=view) [edit]
> add the possibility of issuing commit and rollback toward the database
> If you set autocommit to false, it becomes imposible to issue commit and
> rollback instructions at least to databases that doesn't support COMMIT and
> ROLLBACK as statements. Those database require you to use conn.commit() and
> conn.rollback() instead. With this patch you can write commit or rollback in 
a
> JDBC Request and the JDBC Sampler will translate it to the correct .commit() 
or
> rollback() call.

The patch assumes that a script starting with "commit" or "rollback" contains 
nothing else.

For databases that do allow commit and rollback statements this is 
unnecessarily restrictive.

I think a different approach is needed for databases that don't support these 
commands.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org