将应用程序变量绑定到预备语句中的参数标记。
Bind application variables to parameter markers used in a prepared statement.
事实上，预备语句不是功能，而是原则。
In fact, prepared statement is not a feature but a principle.
清单3将示范如何利用JDBC对预备语句池的支持。
Listing 3 demonstrates how to take advantage of JDBC's prepared statement pooling support.
可以使用SQL命令EXECUTE来执行这个动态预备语句。
This dynamically prepared statement can be executed using the SQL command execute.
我还想进一步根据SQL字符串跟踪预备语句(在执行之前就已经准备就绪)。
I would further like to track performance of prepared statements by the SQL strings that was prepared prior to executing to them.
在创建预备语句（包括可调用语句）时，在创建时捕捉到 SQL字符串参数。
When creating a prepared statement (including a callable statement), the SQL string argument is captured at creation time.
但是，多数应用程序使用预备语句而不是动态sql语句，所以我不想深入这一部分。
However, most applications use prepared statements rather than dynamic SQL statements, so I won't delve into this.
JDBC 3.0让开发人员不再为此担心，因为数据源层现在负责为预备语句进行缓存。
JDBC 3.0 frees the developer from this concern because the data source layer is now responsible for caching prepared statements.
与识别SQL错误的其他机制(比如使用JDBC预备语句)相比，这个特性确实非常方便。
This is a unique feature in comparison with any other mechanism to identify errors in SQL, such as using JDBC prepared statements.
但可惜的是，这也意味着您将不能控制哪个预备语句将被缓冲，而只能控制被缓存的语句的数目。
Unfortunately, this also means that you do not have control over which prepared statements are pooled, only the number of statements that are cached.
事实上，预备语句不是功能，而是原则。和一个自己可以实现它。你所要做的，而不是设计的借口。
In fact, prepared statement is not a feature but a principle. And one can implement it on their own. Which you have to do, instead of devising excuses.
预备语句允许您用一条常用的sql语句然后预编译它，从而在这条语句被多次执行的情况下大幅度地提升性能。
A prepared statement allows you to take a commonly used SQL statement and pre-compile it, thereby dramatically improving performance if the statement is executed multiple times.
dataAPI在后台使用一个预备的语句。
Under the covers, the zero.data API USES a prepared statement.
dataAPI在后台使用一个预备的语句。
Under the covers, the zero.data API USES a prepared statement.
应用推荐