The native queries approach isn't perfect.
原生查询方法并不是完美的。
But HQL does enable you to pass native queries to your underlying database.
但HQL的确可以让你直接向底层数据库传递本地查询。
Finally, you can have named native queries, and map the results back to a POJO.
最后，您可以拥有命名本机查询，并将结果映射回POJO。
For most applications Native Queries will be the better querying interface.
对于大多数应用来讲，原生查询将是更好的查询接口。
As we have seen both Transparent Activation and Native Queries will produce correct results out-of-the-box.
我们已经看到，透明的激活和本地查询都能得到正确的结果。
All further communication with the data source is performed using native queries to the system tables of the data source.
数据源之间所有深层次的交流都是使用数据源系统表的本地查询来实现的。
Of course, inheritance criteria extends into native queries just as strongly as it does the simple object queries I've done so far.
当然，当继承条件扩展到原生查询中时，其功能就跟我所做过的简单对象查询一样强大。
Using native queries with constraints on deep structured objects is straightforward, you can do it just like you would in plain other code.
在深层结构的对象上使用带条件的原生查询是简单的，你可以像你对待其他简单的代码一样完成它。
Native queries provide a powerful way to execute complex queries without having to learn a new query language or resort to complicated object structures to model a predicate.
原生查询为执行复杂查询提供了一种功能强大的方法，而且不需要学习新的查询语言或使用复杂对象结构对谓词建模。
The simplest enhancer task does both: it optimizes Native Queries and it adds the Activatable interface to your classes, making sure a persistent object is activated whenever any field is read.
最简单的增强器任务：优化原生查询而且为类增加可激活接口，以确保无论何时读取任何字段，相应的持久化对象都会被激活。
Most OODBMSs follow the same basic coding conventions and idiomatic expressions, and in fact db4o's support for native queries has spawned an effort to standardize that feature as part of all OODBMSs.
大多数OODBMS 都遵循相同的基本编码约定和惯用表达式，而且实际上db4o对原生查询的支持已逐渐成为一种标准，使该特性成为所有 OODBMS的一部分。
When servicing queries that are complex and mostly read-only, compared to standard relational databases, native XML databases provide faster response times and faster development times.
与标准关系数据库相比，原生xml数据库在服务于主要是只读的复杂查询时能够提供更快的响应时间和开发时间。
The same SPARQL queries can include content contributed by relational databases, REST services, native RDF triplestores and now documents.
同样的SPARQL查询所能包含的内容可以来自于关系数据库、REST服务、本地rdf三元组仓库(triplestores)、以及如今的文档。
Queries over a well-designed, well-implemented native XML database are simply faster than queries over documents stored in a file system, and for several reasons.
查询精心设计和实现的原生xml数据库要比查询存储在文件系统中的文档快得多，原因有几个。
One big advantage of a native XML database is that it can run queries that combine (or join, in SQL parlance) information contained in multiple XML documents.
原生XML数据库一个很大的优点是，可以运行能够将包含在多个 XML 文档中的信息组合在一起的查询（或者按SQL 的说法称为联结）。
Last month, I talked about querying db4o using both native and QBE-style queries.
上个月，我谈到了使用原生和QBE样式的查询来查询db4o。
JPA also enables you to use native SQL queries against the underlying tables, and provides the ability to map back the results.
JPA还使您能够对基础表使用本机SQL查询，并提供映射回结果的能力。
Once connected the agent units interact with the device in native format and translate user queries into SNMP and HTTP responses.
一但链接到代理单元与设备于本地格式有相互影响和转换用户查询到SNMP和HTTP的回应。
You may also express queries in the native SQL dialect of your database.
你也可以直接使用你的数据库方言表达查询。
You may also express queries in the native SQL dialect of your database.
你也可以直接使用你的数据库方言表达查询。
应用推荐