PHP和MySQL ACID程序设计

a while ago I completely recoded my application so that MySQL would perform in an ACID way.

不久之前，我完全重新编写了我的应用程序，以便MySQL以ACID方式执行。

At the very top level of all functions I do something like this:

在所有功能的最顶层我做这样的事情：

        try{
            $db->begin();
            dosomething($_SESSION['userid']);
            $db->commit();
        }catch(advException $e){
            $eCode = $e->getCode();
            $eMessage = $e->getMessage();
            # Success
            if ($eCode == 0){
                $db->commit();
            }else{
                $db->rollback();
            }
        }

Within the function 'dosomething' I have the Exceptions thrown to users like:

在函数'dosomething'中，我向用户抛出了例外：

throw new Exception('There was a problem.',1);

要么

throw new Exception('You have successfully done that!', 0);

So that I can control the flow of the program. If theres a problem then roll back everything that happened and if everything was good then commit it. It's all worked quite great but there's just one flaw that I've come across so far. I added Exception logging so I can see when there are issues that users face. But the problem is, if the table that logs the errors is InnoDB then it's also included in the transaction and will rollback if theres a problem so no errors are stored. To get around this I basically just made the Error logging table MyISAM so when a rollback is done, the changes are still there.

这样我就可以控制程序的流程。如果这是一个问题然后回滚发生的一切，如果一切都很好，然后提交它。这一切都很有效，但到目前为止我遇到的只有一个漏洞。我添加了异常日志记录，因此我可以看到用户遇到的问题。但问题是，如果记录错误的表是InnoDB，那么它也包含在事务中，并且如果存在问题则将回滚，因此不会存储错误。为了解决这个问题，我基本上只是创建了错误记录表MyISAM，因此当回滚完成时，更改仍然存在。

Now I'm thinking of other bits I'd like to keep out of the transaction, like sending a mail within my application to the admin to help alert of problems.

现在我正在考虑其他一些我想要避开的事务，比如在我的应用程序中向管理员发送邮件以帮助提醒问题。

Is there any sort of way for me to not include a database insert within the parent transaction? Have I taken a bad route in terms of Application/DB design and is there any other way I could have handled this?

我有没有办法在父事务中不包含数据库插入？我是否在应用程序/数据库设计方面采取了不好的方法，还有其他方法可以解决这个问题吗？

Thanks, Dominic

谢谢，多米尼克

2 个解决方案

#1

It is not good idea to throw an Exception on success.

成功抛出异常并不是一个好主意。

You have to do DB insert after previous rollback was called.

在调用上一次回滚后，您必须执行数据库插入。

catch (Exception $e) {
  $db->rollback();
  Log::insert('Error: ' . $e->getMessage());
}

Try to use Logger to control your program. It is more flexible way.

尝试使用Logger来控制您的程序。这是更灵活的方式。

2 个解决方案

#1

更多相关文章

随机推荐