如果该列不是一个时间戳，你将不得不做一个值情况语句。
If the values of that column are not a time stamp you will have to do a CASE statement.
另外，给出了一个例子，演示如何通过分析跟踪找到一个死锁情况所涉及的sql语句。
In addition, it provided an example showing how to find the SQL statements involved in one deadlock situation by analyzing the traces.
只有在两条 SQL语句都能够成功更新表的情况下，事务才会得到成功调用。
This transaction can only be called successful if both SQL statements were able to update the table successfully.
SQL语句分布图显示数据库的动态和静态 SQL语句的分布情况。
SQL statement distribution shows the distribution of dynamic and static SQL statements for a database.
在使用当前这组索引的情况下，sql语句的运行是否正常？
Are the SQL statements running well with the current set of indexes?
这种情况下，强烈建议读者使用原生的CLRPFM命令，而不是SQLdelete语句。
In these cases, it strongly recommend that the reader USES the native CLRPFM command rather than the SQL DELETE statement.
清单2展示了在不使用完整语句的情况下把简单值嵌入到页面中的示例。
Listing 2 has an example of embedding simple values into a page without using complete statements.
其中嵌入了应对没有可供删除的数据这种情况的异常处理语句，使得程序更健壮一点。
The program has nested exception handling to deal with situations in which it looks up nonexistent data to delete, making the program a bit more robust.
在大多数情况下，非常适合使用参数标记的sql语句要么是非常简单的SELECT语句(只引用一个表)，要么是被多次执行的INSERT、UPDATE和DELETE (uid)操作。
In most cases, well-suited SQL statements are very simple SELECT statements that reference only a single table or are INSERT, UPDATE, and DELETE (UID) operations that are executed many times.
需要注意的是，在某些情况下给定的select语句不能使用FOR update子句。
It should be noted that there are situations where the for UPDATE clause is not available for a given SELECT statement.
在这种情况下，使用自己指定的查询语句并填充才是明智之举。
In this particular situation, it makes sense for you to use the same table and fill it with a more specific query.
产生的页面显示sql语句的详细执行情况。
The resulting page displays a detailed profile of an SQL statement execution, selected through drill down.
这意味着必须修改最后一个IF 语句，允许只有用户名的情况，但是这个逻辑只适用于SSO。
That implies we'd have to change the final if statement considerably to allow for user name only, but only in the case of SSO.
考虑更现实的情况，h1和h2语句是分隔在大量css样式表中的数百行。
Consider the more realistic case, where the h1 and h2 statements are hundreds of lines apart in a massive CSS stylesheet.
一般情况下，使用以下语句创建对象。
如果查询可以简化为一条单独的语句，未进行优化的情况下，Sequel的执行效果相对要差，反之会优于ActiveRecord。
If this could be simplified into a single statement, Sequel performs worse if you don't optimize, and better if you do.
清单5展示了merge语句的其他的使用情况，其中WHENMATCHED和WHENNOT matched子句是可选的。
Listing 5 shows other usages of the merge statement where the WHEN MATCHED and WHEN NOT MATCHED clauses are optionally used.
要避免这种情况，使用CREATEPROCEDURE语句的returns子句来将数据返回给调用者。
To avoid this scenario, use the RETURNS clause of the CREATE PROCEDURE statement to return data to the caller.
某些情况下，如果语句包含主机变量、参数标记或特殊寄存器那么访问路径在运行时的性能不会很好。
In some cases, the access path does not perform well at runtime if the statement contains host variables, parameter markers, or special registers.
在这种情况下，他们可以发出一条select语句来识别符合条件的行，然后再DELETE那些行。
In this case, they can issue a SELECT statement to identify rows that qualify then DELETE those rows.
可以使用链接向下钻取到每个语句，了解每个语句执行情况的详细信息。
You can drill down into each statement using links to get detailed information about each statement execution.
创建了游标后，您可以通知它向您提供下一个记录，在种情况下，它会按sql语句指定的顺序向记录列表下方移动。
After you have the cursor, you can tell it to give you the next record, in which case it moves down the list of records, in the order specified by the SQL statement.
在这样的情况下，可以使用分号来分隔单个语句。
In these cases, you can use semicolons to separate individual statements.
最佳实践应是对日志语句加以保护，使其仅在出错和进行调试的情况下打开。
It is a good practice to guard log statements so they are turned on during error and debugging situations only.
您还会注意到，我不需要在语句之间(除了特定情况下)加入语句分隔符，像分号。
You will also notice that I don't need to put statement separators, like semicolons, in between statements except in certain cases.
乐观事务锁不能用于在单个update语句中更新数据行集合，因此在这种情况下，很难进行错误处理。
Optimistic transaction locking should not be used to update sets of rows in a single update statement, as error handling in this case is very difficult.
在这些情况下，脚本以值或返回语句结束。
In these cases, the script ends with a value or a return statement.
避免准备阶段在下面两种情况下最有用：一是sql语句被多次执行；二是准备阶段需要的时间占语句总执行时间的很大一部分。
Avoiding the prepare phase especially pays off if an SQL statement is executed many times and if the prepare phase makes up a significant portion of the statement's overall execution time.
如下例所示，在此情况下，查询语句获得用户的名称和电子邮件地址。
In this scenario a query gets the name and e-email address from a user, as in the following example.
如下例所示，在此情况下，查询语句获得用户的名称和电子邮件地址。
In this scenario a query gets the name and e-email address from a user, as in the following example.
应用推荐