System and method for optimizing transaction termination

• US 20060074877A1
• Filed: 10/01/2004
• Published: 04/06/2006
• Est. Priority Date: 10/01/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Kuersch, Ralf, Theobald, Dietmar, Raupp, Thomas
• Granted Patent: US 8,655,853 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2455 Query execution

Abstract

Embodiments of the invention are generally directed to a system and method for optimizing transaction termination. A database interface receives an indication to terminate a transaction. The database interface decides whether to send a command to the underlying database server to terminate the transaction. If the database interface does send a command to the database server, it determines which command is appropriate to send.

Claims

1. A method comprising:

receiving an indication to adjust a transaction state of a database connection;

determining a database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection;

transitioning to one of a plurality of transaction states based, at least in part, on the determined database statement type;

receiving an indication to terminate a transaction associated with the database connection; and

determining whether to send a termination request to a database based, at least in part, on the transaction state of the database connection.

2. The method of claim 1, wherein receiving the indication to adjust the transaction state of the database connection comprises one or more of:

receiving a call to a prepareStatement method of the database connection;

or

receiving a call to an execute method of a statement object derived from the database connection.

3. The method of claim 2, wherein determining the database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection comprises determining that the statement type is one of:

an INSERT statement;

an UPDATE statement;

a DELETE statement;

a SELECT_FOR_UPDATE statement;

or

a SELECT statement.

4. The method of claim 3, further comprising, if the statement type is a SELECT statement, determining whether the SELECT statement is one of the following:

a SELECT statement that does not cause the database to allocate a resource based, at least in part, on a current transaction isolation level; and

a SELECT statement that causes the database to allocate a resource based, at least in part, on the current transaction isolation level.

5. The method of claim 4, wherein transitioning to one of the plurality of transaction states based, at least in part, on the determined database statement type comprises one of:

transitioning to a first state, if the SELECT statement causes the database to allocate the resource;

transitioning to a second state, if the SELECT statement does not cause the database to allocate the resource; and

transitioning to the second state, if the database statement type is a SELECT_FOR_UPDATE statement.

6. The method of claim 5, wherein the resource is a database lock.

7. The method of claim 5, wherein receiving the indication to terminate the transaction comprises one or more of:

receiving a call to a commit method;

receiving a call to a rollback method;

receiving a call to enable an auto-commit mode of the transaction;

or

receiving a call to a close method.

8. The method of claim 7, wherein determining whether to send the termination request to the database based, at least in part, on the selected transaction state comprises determining that the termination request is not to be sent to the database, if the transaction state is the first state.

9. The method of claim 7, wherein determining whether to send the termination request to the database based, at least in part, on the selected transaction state comprises determining that the termination request is to be sent to the database, if the transaction state is the second state.

10. The method of claim 9, further comprising selectively sending one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction.

11. The method of claim 10, wherein selectively sending one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction comprises:

sending a commit call to the database, if the indication to terminate the transaction is a call to a rollback method; and

sending a commit call to the database, if the indication to terminate the transaction is a call to enable the auto-commit mode of the transaction.

12. The method of claim 3, wherein transitioning to one of the plurality of transaction states based, at least in part, on the determined database statement type comprises transitioning to a third transaction state if the database statement type is one of:

an INSERT statement;

an UPDATE statement; and

a DELETE statement.

13. The method of claim 12, wherein receiving the indication to terminate the transaction comprises one or more of:

receiving a call to a commit method;

or

receiving a call to a rollback method.

14. The method of claim 13, wherein determining whether to send the termination request to the database based, at least in part, on the selected transaction state comprises one of:

propagating the call to the commit method to the database, if the transaction state is the third state; and

propagating the call to the rollback method to the database, if the transaction state is the third state.

15. A database connection management system comprising:

a database connection handle associated with a physical database connection having an internal variable to represent a transaction state of the physical database connection; and

logic to

receive an indication to adjust the transaction state of the internal variable;

determine a database statement type based, at least in part, on the received indication to adjust the transaction state of the internal variable;

transition to one of a plurality of transaction states based, at least in part, on the determined database statement type;

receive an indication to terminate a transaction; and

determine whether to send a termination request to an underlying database based, at least in part, on the transaction state of the database connection.

16. The system of claim 15, wherein the logic to determine the database statement type based, at least in part, on the received indication to adjust the transaction state of the internal variable comprises logic to determine that the statement type is one of:

an INSERT statement;

an UPDATE statement;

a DELETE statement;

a SELECT_FOR_UPDATE statement;

or

a SELECT statement.

17. The system of claim 16, wherein, if the statement type is a SELECT statement, further comprising logic to determine whether the SELECT statement is one of:

a SELECT statement that does not cause the underlying database to allocate a resource based, at least in part, on a current transaction isolation level; and

a SELECT statement that causes the underlying database to allocate a resource based, at least in part, on the current transaction isolation level.

18. The system of claim 17, wherein the logic to transition to one of a plurality of transaction states based, at least in part, on the determined database statement type comprises logic to:

transition to a first state, if the SELECT statement causes the database to allocate the resource;

transition to a second state, if the SELECT statement does not cause the database to allocate the resource; and

transition to the second state, if the database statement type is a SELECT_FOR_UPDATE statement.

19. The system of claim 18, wherein the logic to receive the indication to terminate the transaction comprise logic to perform one or more of:

receive a call to a commit method;

receive a call to a rollback method;

receive a call to enable an auto-commit mode of the transaction;

or

receive a call to a close method.

20. The system of claim 19, wherein the logic to determine whether to send the termination request to the database based, at least in part, on the selected transaction state comprises logic to determine that the termination request is not to be sent to the database, if the transaction state is the first state.

21. The system of claim 19, wherein the logic to determine whether to send the termination request to the database based, at least in part, on the selected transaction state comprises logic to determine that the termination request is to be sent to the database, if the transaction state is the second state.

22. The system of claim 21, further comprising logic to selectively send one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction.

23. The system of claim 22, wherein the logic to selectively send one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction comprises logic to:

send a commit call to the database, if the indication to terminate the transaction is a call to a rollback method; and

send a commit call to the database, if the indication to terminate the transaction is a call to enable the auto-commit mode of the transaction.

24. A system comprising:

means for receiving an indication to adjust a transaction state of a database connection;

means for determining a database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection;

means for transitioning to one of a plurality of transaction states based, at least in part, on the determined database statement type;

means for receiving an indication to terminate a transaction associated with the database connection; and

means for determining whether to send a termination request to a database based, at least in part, on the transaction state of the database connection.

25. The system of claim 24, wherein the means for determining the database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection comprises determining that the statement type is one or more of:

an INSERT statement;

an UPDATE statement;

a DELETE statement;

a SELECT_FOR_UPDATE statement;

or

a SELECT statement.

26. The system of claim 25, further comprising, if the statement type is a SELECT statement, means for determining whether the SELECT statement is one of the following:

a SELECT statement that does not cause the database to allocate a resource based, at least in part, on a current transaction isolation level; and

a SELECT statement that causes the database to allocate a resource based, at least in part, on the current transaction isolation level.

27. The system of claim 26, wherein the means for transitioning to one of the plurality of transaction states based, at least in part, on the determined database statement type comprises:

means for transitioning to a first state, if the SELECT statement causes the database to allocate the resource;

means for transitioning to a second state, if the SELECT statement does not cause the database to allocate the resource; and

means for transitioning to the second state, if the database statement type is a SELECT_FOR_UPDATE statement.

28. The system of claim of 27, wherein the means for receiving the indication to terminate the transaction comprises one or more of:

means for receiving a call to a commit method;

means for receiving a call to a rollback method;

means for receiving a call to enable an auto-commit mode of the transaction;

or

means for receiving a call to a close method.

29. The system of claim 28, wherein the means for determining whether to send the termination request to the database based, at least in part, on the selected transaction state comprises means for determining that the termination request is not to be sent to the database, if the transaction state is the first state.

30. The system of claim 28, wherein the means for determining whether to send the termination request to the database based, at least in part, on the selected transaction state comprises means for determining that the termination request is to be sent to the database, if the transaction state is the second state.

31. The system of claim 30, further comprising means for selectively sending one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction.

32. The system of claim 31, wherein the means for selectively sending one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction comprises:

means for sending a commit call to the database, if the indication to terminate the transaction is a call to a rollback method; and

means for sending a commit call to the database, if the indication to terminate the transaction is a call to enable the auto-commit mode of the transaction.

33. An article of manufacture comprising:

an electronically accessible medium providing instructions that, when executed by an apparatus, cause the apparatus to

receive an indication to adjust a transaction state of a database connection;

determine a database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection;

transition to one of a plurality of transaction states based, at least in part, on the determined database statement type;

receive an indication to terminate a transaction associated with the database connection; and

determine whether to send a termination request to a database based, at least in part, on the transaction state of the database connection.

34. The article of manufacture of claim 33, wherein the instructions that, when executed by the apparatus, cause the apparatus to determine the database statement type based, at least in part, on the received indication to adjust the transaction state of the database connection cause the apparatus to determine that the statement type is one of:

an INSERT statement;

an UPDATE statement;

a DELETE statement;

a SELECT_FOR_UPDATE statement;

or

a SELECT statement.

35. The article of manufacture of claim 34, wherein the electronically accessible medium provides further instructions that, when executed by the apparatus, cause the apparatus to determine whether the SELECT statement is one of the:

a SELECT statement that does not cause the database to allocate a resource based, at least in part, on a current transaction isolation level; and

a SELECT statement that causes the database to allocate a resource based, at least in part, on the current transaction isolation level.

36. The article of manufacture of claim 35, wherein the instructions that, when executed by the apparatus, cause the apparatus to transition to one of the plurality of transaction states based, at least in part, on the determined database statement type cause the apparatus to perform one of:

transition to a first state, if the SELECT statement causes the database to allocate the resource;

transition to a second state, if the SELECT statement does not cause the database to allocate the resource;

or

transition to the second state, if the database statement type is a SELECT_FOR_UPDATE statement.

37. The article of manufacture of claim 36, wherein the instructions that, when executed by the apparatus, cause the apparatus to receive the indication to terminate the transaction cause the apparatus to perform one or more of:

receive a call to a commit method;

receive a call to a rollback method;

receive a call to enable an auto-commit mode of the transaction;

or

receive a call to a close method.

38. The article of manufacture of claim 37, wherein the instructions that, when executed by the apparatus, cause the apparatus to determine whether to send the termination request to the database based, at least in part, on the selected transaction state cause the apparatus to:

determine that the termination request is not to be sent to the database, if the transaction state is the first state.

39. The article of manufacture of claim 37, wherein the instructions that, when executed by the apparatus, cause the apparatus to determine whether to send the termination request to the database based, at least in part, on the selected transaction state cause the apparatus to:

determine that the termination request is to be sent to the database, if the transaction state is the second state.

40. The article of manufacture of claim 37, wherein the electronically accessible medium provides further instructions that, when executed by the apparatus, cause the apparatus to:

selectively send one of a plurality of termination requests to the database based, at least in part, on the indication to terminate the transaction.