Prepared statements and Cursors.
准备查询语句以及游标。
Using prepared statements with a cursor.
结合使用准备好的语句和游标。
Prepared statements and stored procedures.
预处理语句和存储过程。
Automatic re-compilation of prepared statements.
预编译语句的自动重新编译。
Do prepared statements persist between requests?
做准备的请求之间持续的陈述？
Prepared statements are a subclass of the statement class.
预置语句是statement类的一个子类。
In short, prepared statements use fewer resources and thus run faster.
简言之，预处理语句使用更少的资源，因而运行得更快。
In prepared statements, Nokia declared victory and Apple expressed relief.
诺基亚通过事先准备好的声明宣布了胜利，而苹果则表达了解脱之感。
You can create and execute prepared statements or create and run external scripts.
您可以创建并执行准备好的语句，或创建并运行外部脚本。
This parameter controls the maximum number of prepared statements cached by a connection pool.
该参数控制由连接池缓存的最大预编译语句数。
The parameters to prepared statements don't need to be quoted; the driver handles it for you.
提供给预处理语句的参数不需要用引号括起来，驱动程序会处理这些。
Another task you don't normally associate with the command line is the use of prepared statements.
通常您不会联系到命令行的另外一项任务就是使用准备好的语句。
You can even create prepared statements that can be used with multiple sets of data (see Listing 8).
您甚至可以创建与多个数据集一起使用的准备好的语句(参见清单8)。
Prepared statements can be significantly faster than regular queries depending on the database being used.
准备语句相比普通查询来说要快很多，当然跟使用的数据库有关系。
If your application exclusively USES prepared statements, you can be sure that no SQL injection will occur.
如果应用程序独占地使用预处理语句，那么可以确保没有SQL入侵发生。
In a nutshell, short queries and OLTP transactions are faster as prepared statements with parameter markers.
总而言之，短小的查询和OLTP事务就像含参数占位符的预置语句一样，具有更快的速度。
However, most applications use prepared statements rather than dynamic SQL statements, so I won't delve into this.
但是，多数应用程序使用预备语句而不是动态sql语句，所以我不想深入这一部分。
JDBC 3.0 frees the developer from this concern because the data source layer is now responsible for caching prepared statements.
JDBC 3.0让开发人员不再为此担心，因为数据源层现在负责为预备语句进行缓存。
I would further like to track performance of prepared statements by the SQL strings that was prepared prior to executing to them.
我还想进一步根据SQL字符串跟踪预备语句(在执行之前就已经准备就绪)。
This is a unique feature in comparison with any other mechanism to identify errors in SQL, such as using JDBC prepared statements.
与识别SQL错误的其他机制(比如使用JDBC预备语句)相比，这个特性确实非常方便。
Prepared statements are recompiled for better performance and are convenient when you need to do the same thing over and over again.
准备好的语句可重新编译，从而获得更好的性能，在您反复执行同一操作时，它非常方便。
Perhaps the most useful prepared statements are those that not only take input values, but also operate on the current row of a cursor.
或许最有用的准备好的语句不仅可以获取输入值，而且还可以对游标的当前行进行操作。
As with prepared statements in a JDBC application, the values get substituted for each placeholder in order of appearance in the statement.
与JDBC应用程序中的准备好的语句一样，值可以按在语句中出现的顺序被各占位符取代。
If your JDBC program USES prepared statements and parameter markers, queries are processed faster if they are found in the database statement cache.
如果您的JDBC程序使用已经准备好的语句和参数标志，并且如果在数据库语句缓存中找到了它们的话，查询过程将处理地更快。
Unfortunately, this also means that you do not have control over which prepared statements are pooled, only the number of statements that are cached.
但可惜的是，这也意味着您将不能控制哪个预备语句将被缓冲，而只能控制被缓存的语句的数目。
You can view when relevant elements such as JDBC connections, statements, prepared statements, and result sets, were created and which queries were issued.
您可以查看创建了哪些相关元素，比如jdbc连接、语句、已备语句和结果集，以及发起了哪些查询。
If prepared statements are involved, the differences could increase or decrease, depending on your application, system configuration and data involved.
如果使用了预置语句，那么两种方法之间的差距可能拉大，也可能缩小，这取决于您的应用程序、系统配置和数据。
Since most database layers support prepared statements that handle this risk much better, turning this off will again remove an annoying performance problem.
由于大部分数据库层支持能更好地处理该风险的准备语句，禁用该设置会再次消除这个烦人的性能问题。
Since most database layers support prepared statements that handle this risk much better, turning this off will again remove an annoying performance problem.
由于大部分数据库层支持能更好地处理该风险的准备语句，禁用该设置会再次消除这个烦人的性能问题。
应用推荐