Closed HowardLing2119 closed 4 years ago
I am not sure whether this is mentioned in the project specifications, care to provide any reference documented in the course project?
You make your point so I think I have to confirm whether it is a bug or not with TA.
Below is my argument. As mentioned in 7. , a transaction must be atomic, consistent, isolated and durable -- summarized as the ACID acronym. In the ACID acronym, atomicity means that all operations either succeed or all of them fail, referring to the lecture note Middleware: Enabling distributed computing P.17. An empty transaction cannot have a fail operation so it should be committed successfully, same as how MySQL handles an empty transaction.
TA Verified: This is not considered as a bug.
In transaction behaviors, when you start a transaction, even you do not run any statement, you can still commit. But the server returns 400 for committing an empty transaction. You can try with the test case below. https://trial-howard-20200221.s3.ap-east-1.amazonaws.com/Empty+Transaction+400+.jmx