这是处理数据库异常的一种更好的方法。
数据库异常关闭后，重起时，恢复关闭时的任何作业。
Upon database startup after an abnormal database shutdown, recovers any jobs that were running.
这是因为一些数据库被配置为会杀掉长时间空闲的连接，网络或数据库相关的异常也可能会杀死连接。
This is because some databases are configured to kill long idle connections and a network or database related exception may also kill a connection.
BSU为实例和数据库分配内存，拦截和处理信号，并处理发送到DB2的异常。
BSUs allocate memory for the instance and database, intercept and handle signals, and handle exceptions sent to DB2.
通过分析跟踪文件，您可以检测异常的应用程序行为，比如数据库资源漏泄。
By analyzing the trace files, you can detect abnormal application behavior, such as database resource leaks.
为了正确地考虑所有错误，需要能够将异常连接在一起，从而让进行调用的代码知道数据库遇到的所有问题。
To properly account for all of them, you need to be able to tie exceptions together so that the calling code is notified of all the problems the database encountered.
为了看到使用不正确映射时抛出的异常，需要在您选择的厂商的软件上创建一个数据库，然后根据上面描述的把当前的后端ID设置为不正确的值。
To see exceptions generated by using the improper mapping, create a database in the vender software of your choice, then set the current backend ID value as instructed above to the incorrect value.
值得注意的是，除非您捕捉从构造函数抛出的异常，否则，如果php脚本未能连接到数据库，它将终止。
It's worth noting that, unless you catch exceptions that are thrown from the constructor, your PHP script will terminate if it could not connect to the database.
延迟抓取的另一个问题就是在获取到请求的数据前要一直打开数据库连接，否则应用就会抛出一个延迟加载异常。
Another issue with lazy fetching is that the database connection has to be retained until all the required data is fetched else the application will throw a lazy loading exception.
当超出限制的时候，数据库就会开始拒绝读写，根据微软的建议，开发者必须通过通过异常处理以编程的方式处理这种情况。
When limits are exceeded the database will begin rejecting reads and writes and the developer must handle this programmatically through exception handling as suggested by Microsoft.
日志服务接收所有的日志请求，将它们保存在日志数据库中，并将它们转发给异常解解决服务。
Logging service accepts all logging requests, stores them into logging database and forwards them to the Exception Resolution service.
在多个查询语句的执行过程中需要保持数据库连接，否则会抛出一个延迟加载异常，这将导致数据出现问题。
Database connection needs to be maintained for the duration of the multiple query cycle else a lazy loading exception is thrown, resulting in inadequate use of resources.
将异常信息存储到未确认其状态的FEM数据库。
The exception information is stored to the FEM database with a status of not confirmed.
查阅数据库手册，搜索异常中返回的错误码，从而判断失败的原因。
Identify cause of the failure by going through database manuals and searching for the error codes sent back in the exception.
您创建了零件数据库，并设置了维护窗口，配置了异常状况下的电子邮件联系方式。
You created a parts database. You also set up a maintenance window and configured an E-mail contact in case something goes wrong.
通常，一种优秀的实践就是不要在关系数据库中使用null(即没有值)列，因为当您试图读取这类列时，您将得到一个null值异常。
A general, good practice is not to allow null (that is, no value) columns in a relational database, because when you attempt to read such a column, you get a null value exception.
系统级错误包括语法错误、空指针异常、web服务超时、数据库连接超时等。
The system level error includes syntactical error, null pointer exception, web service timeout, database connection timeout, and so on.
重新引导Geronimo将更正一次错误，但随后再次访问数据库时又会生成异常。
Rebooting Geronimo will correct the error for one, but then generate the exception again when the database is accessed by the other.
Derby关闭数据库时，将抛出SQLException，使用08006作为SQLState，这就是catch块忽略此异常的原因。
When Derby shuts down a database, it throws an SQLException with an SQLState of 08006, which is why the catch block ignores this exception.
如果你现在关注到几乎各行各业的公司——请看看UPS、FedEx、MasterCard——都有自己的实时数据库，而且异常强大。
If you look at most businesses now, pretty much everyone - think of UPS, FedEx, MasterCard - has a real-time database. And that's powerful.
如果对惰性关联执行查询，但是没有相关联的数据库连接，Hibernate就会抛出LazyInitializationException异常。
Hibernate throws a LazyInitializationException because the query is executed for the lazy association, and no connection to the database is associated with it.
我们将创建一个症状数据库，该数据库描述这个应用程序异常以及改正该问题所需的步骤。
We will build a symptom database that describes this application exception and the steps required to remedy the problem.
如果服务器脚本不检查数据，要么数据库抛出异常，要么数据库安全会受到影响。
If the server script does not check the data, either the database will throw an exception or the database will be compromised.
在处理SQL异常时，惟一的难点是正确地回收数据库资源，比如数据库连接。
The only major difficulty in dealing with SQL exceptions is the proper reclamation of database resources, such as the database connection.
这仅仅是一些可能的异常，但根据硬件和数据库，您可以使用该测试生成的大量异常。
These are only some possible exceptions, but based on the hardware and database, you are using a wide variety of exceptions that can be produced by this test.
出现多个警告或异常的原因很简单：在数据库中事件常常连接在一起。
The reason for the chaining is simple: Events are often coupled within a database.
注意，如果每件事都按计划进行，那么在每件事都成功提交到数据库，而且没有抛出异常之后，result变量应当等于true。
Notice that if everything goes as planned, the result variable will equal true after everything is successfully submitted into the database and no exceptions are thrown.
通过这种方式调用该方法总是会导致抛出一个Exception，该异常指出数据库被关闭。
Calling this method in this way always results in an Exception being thrown that indicates that the database was shutdown.
但是，如果发生异常，则调用compensate方法，它会处理所有已经提交到数据库的活动的反转操作。
However, if an exception occurs, you invoke the compensate method, which takes care of reversing whatever activities have been committed to the database.
如果数据库不存在，将抛出一个异常，并且DBManager构造函数自己将创建数据库。
If the database doesn't exist, an exception is thrown, and the DBManager constructor creates the database itself.
应用推荐