获得某一个命名的查询变量。
Checks the return from the named query.
检查从已命名查询返回的结果。
To correct this, I use a Hibernate named query.
为更正该问题，我使用了Hibernate命名查询。
Uses these three parameters to call the named query SLAEndpointLookup.
使用这3个参数来调用已命名查询SLAEndpointLookup。
I can easily wrap the named query in a method and execute it again and again.
我可以方便地将命名查询打包在一个方法中，并重复执行它。
Add a named query for each finder method to the hbm.xml mapping file for the domain object.
将每个查找器的命名查询添加到域对象的hbm . xml映射文件。
The query Statement area shows the actual named query that will be performed by this method.
QueryStatement区域显示出了，该方法将会采用的实际已命名查询。
Extracts the three parameters for the named query from specific locations in the SOAP Header.
从SOAPHeader中的特定位置提取已命名查询的3个参数。
Below is an example of how you can define a named query and associate it with an entity class.
下面是如何定义命名查询，并将其与实体类关联的一个示例？
The arguments for a query operation are the JPQL string or moniker of a predefined named query.
查询操作的参数是JPQL字符串或预定义名称查询的别名。
The sample's result resolver will then resolve this statement to a named query which we predefined as.
这个样例的结果解析器然后将这个语句解析为一个我们预先定义的已命名查询。
There will be a corresponding query method for each named query that was created on the Department entity.
Department实体创建的每一个已命名查询，都将会有一个与之相对应的查询方法。
The major benefit is the externalization and, therefore, an annotated named query makes little sense, if any.
其主要优点是查询的外部化，因此，带注释的命名查询(如果有)几乎没有任何意义。
It keeps you from having to change all references to a query if you happen to change the named query itself.
如果您想要改变已命名查询自身的话，它能使您避免更改所有的参考。
Initialises the handler with the values for the three parameters to be used in the named query called from the mediation.
使用从中介流调用的已命名查询中使用的3个参数的值初始化处理程序。
With a named query properly defined, the application can execute the query and apply business logic to the returned results.
正确定义好一个已命名的查询之后，应用程序就可以执行该查询并向返回的结果应用业务逻辑。
Although defining a named query as an annotation can make it more reusable in the code, the benefit is so minimal that it is essentially useless.
命名查询是外部化查询的好方法。尽管将命名查询定义为注释可以使查询在代码中得到更多重用，但是优点很少，在本质上没有使用价值。
The with clause allows for the definition of a named query within a statement, which can be referred to at a later point in the same statement.
with子句允许在一条语句中定义一个有名称的查询，在同一条语句中，稍后将引用到这个查询。
If you don't add any additional metadata, Hades will try to lookup a JPA named query of the form {entity}. {method-name} and use that if available.
如果你没有增加任何附加的元数据，Hades会尝试查找格式为{entity}. {method - name}的JPA查询方法，如果有效的话就使用该方法。
You can define a named query as an annotation and execute it somewhere else in the code. Here is an example of using executing this type of named query.
您可以将命名查询定义为注释，并在代码中的其他位置执行它。
This collection resolver looks up the named query as provided by the user, attaches the position parameters, and executes JDBC statements against the database.
这个集合解析器查询用户提供的已命名查询，附加位置参数，并针对数据库执行JDBC语句。
The LET clause extracts referenced entity information from the collection of credit default swap data that DB2 returns after executing the named query defined in Listing 6.
let子句从执行清单6中定义的已命名查询之后DB 2返回的信用违约掉期数据集合中摘取所引用的实体信息。
Other scenarios may require a non-zero query depth. Save the updated named query file as SLAEndpointLookup.xml and then import it into WebSphere Service Registry and repository.
而其他场景可能需要一个非零查询深度。
How these identifiers are used and defined is specific to your own installation, but an understanding of how these are used in this named query should inform your naming strategy.
这些标识符的使用和定义方式特定于您自己的安装，但是对这些标识符在这个已命名查询中的使用方式的理解应该告知您的命名策略。
You can add additional search criteria if needed for your installation. The WebSphere Service Registry and Repository query is activated in the named query using these parameters.
如果需要，您可以为您的安装添加额外的搜索标准。
The query depth for our named query SLAEndpontLookup is set to 0, which means that the endpoints are returned with just properties and classifications -- no relationships are populated.
我们的已命名查询SLAEndpontLookup的查询深度设置为 0，这意味着返回的端点只带有属性和类别 —没有填充关系。
The definition of a named Topic Diagram can be persisted so that the same query can be rerun at any time.
一个被命名的主题图的定义能够被保持，从而能够在任何时间都返回相同的查询。
In such a case, the graph pattern is applied to each of the named graphs available to the query.
在这种情况下，图形模式被应用到查询可以使用的每个命名图中。
Each matching binding of the graph pattern's variables to the model's nodes becomes a query solution, and the values of the variables named in the SELECT clause become part of the query results.
将每个图形模式变量的绑定与模型节点进行匹配就成为一种查询解决方案，而select子句中指定的变量值则成为查询结果的一部分。
Listing 11's graph clause matches on each person node in the named FOAF graphs given to the query.
清单11的graph子句和提供给查询的命名图中的每个人员节点匹配。
应用推荐