Problems with annotated named queries.
使用带注释的命名查询所带来的问题。
Refactoring support for relationships and named queries
获得关系以及已命名查询的支持
Named queries are just one example of how annotations can be overused.
命名查询只是注释如何被过度使用的一个示例。
I have chosen to use named queries to illustrate a much larger problem.
我选择使用命名查询来说明一个更大的问题。
Hibernate provides no real namespace functionality for the named queries.
Hibernate不为命名查询提供任何真正的名称空间功能。
All of the named queries have been added as NamedQuery annotations on the entity.
所有已命名的查询在实体上被添加了Named Query注释。
It also generates the SQL statements needed in the execution of JPA named queries.
它还生成在jpa命名的查询的执行中需要的sql语句。
It USES named queries to resolve the remainder of the URI and executes appropriate logic.
它使用已命名的查询来解析uri的其余部分并执行适当的逻辑。
Now, I can easily make changes to named queries without changing my source code and recompiling.
现在，我可以方便地对命名查询进行更改，而无需更改源代码和重新编译。
Will perform validation on all named queries at initialization time, and throw if any is not valid.
对所有的命名查询在初始化的时候执行验证，任何无效的查询会抛出异常。
In Listing 7, you can see where we instantiate this resolver after defining some basic named queries.
在清单7中，我们在定义了一些基本的已命名查询后实例化这个解析器。
Named queries enable you to define a query in a single location. There are many benefits to named queries.
命名查询使您能够在单个位置定义一个查询。
If this option is enabled, named queries will be generated into the appropriate entities, and the JPA Manager Bean query methods will use them.
如果该选项能用，在合适的实体中将生成已命名的查询，而且JPAManagerBean查询方法将使用它们。
In this commentary, I will examine the various query styles in JPA, rationalize why they exist, and explain why certain styles (such as named queries) just make no sense to be annotated.
在本文中，将检查JPA中的各种查询样式，解释它们存在的原因，并解释为什么对某些样式（如命名查询）进行注释没有任何意义。
Queries may also use background data in conjunction with named graphs.
查询也可以把后台数据和命名图结合在一起使用。
In the above example, we used numbered parameters, but you can also use named parameters for more complicated queries.
在上例中，使用了编号的参数，但是也可以使用指定参数以进行更复杂的查询。
Definition of parameterized queries that can take parameters as an ordered list, referred to by index Numbers, or as named parameters referred to by name.
定义参数化的查询，这种查询可以以有序列表形式接收参数(按索引号引用参数)，也可以采用按名称引用的命名参数。
Finally, you can have named native queries, and map the results back to a POJO.
最后，您可以拥有命名本机查询，并将结果映射回POJO。
In the chart named popular queries, you can find the popular keywords in the order in which they were searched.
在名为热门查询的图表中，可以看到热门关键字按搜索顺序排列。
In the chart named number of queries, you can track the count of queries based on the date, week, month, or specified period.
在名为查询数量的图表中，可以基于日、周、月或特定时间段追踪查询数。
You can configure mysqld to log slow queries in the aptly named slow query log.
您可以配置mysqld将这些慢速查询记录到适当命名的慢速查询日志中。
This enables queries for arbitrary countries where all named countries (from both rules) will be found, but queries for countries that are part of the G8 group are also possible.
这样的话，对任意国家的查询将会找到这两个规则中指定的所有国家，同时也可以查询属于八国集团的国家。
The following example queries the attachment configuration for queue AMDC79_ps for a field named add_queue.
下面的示例查询针对名为 add_queue 的字段查询队列 AMDC79_ps 的连接配置。
The JSP, named references.jsp, queries a table of Apache Geronimo references available in the database, as shown in Figure 1.
该JSP（名为references.jsp）将查询数据库中可用的ApacheGeronimo引用的表，如图1 中所示。
The runtime queries the Permission class about its implication reasoning logic by calling a method, aptly named implies.
运行时通过调用一个恰当地取名为implies的方法来查询permission类的隐含推断逻辑。
The core of the BIND service is a daemon called named (or in.named), which handles all of the queries.
BIND服务的核心是一个名为named(或in . named)的守护进程，此守护进程处理所有的查询。
Group members without Named users queries for members of a group, but removes a set of users from the result set.
GroupMemberswithoutNamedUsers用于查询一个组的成员，但从结果集中删除一组用户。
Named SQL queries may be defined in the mapping document and called in exactly the same way as a named HQL query.
可以在映射文档中定义SQL查询的名字，然后就可以像调用一个命名HQL查询一样直接调用命名SQL查询。
The authors roughly segment the queries according to their Web context and use the Web data to train a complex named-entities classifier.
根据用户的查询在网络中的上下文数据，将查询进行粗切分，并利用该网络数据作为训练语料训练复杂专名分类器。
The authors roughly segment the queries according to their Web context and use the Web data to train a complex named-entities classifier.
根据用户的查询在网络中的上下文数据，将查询进行粗切分，并利用该网络数据作为训练语料训练复杂专名分类器。
应用推荐