我可以问几个问题吗?
我问道,“这是真的吗?”
我能问你几个问题吗?
我怀疑他是否值得信赖。
为什么我查询不到结果?
I query his ability to do the job.
我对他是否有能力干这份工作表示怀疑。
I query whether it is right to do so.
我怀疑那样做是否正确。
I query whether his word can be relied on.
我怀疑他的话是否可靠。
I query whether his words can be relied on.
我询问他的话是否可靠。
Now when I query the bands collection, I should see this.
现在我查询bands集合时,我应该看到。
I query very much whether it is wise to act so hastily.
我真怀疑如此操之过急地行动是否明智。
After creating a word, I query the dictionary instance for the same word to confirm it made it into the database.
创建单词后,我查询这个单词的dictionary实例以确认它被加入了数据库。
But what I am unable to find is how do I query the API to simply return all the cities, which will then subsequently allow me to populate my list view, then allowing the user to see the temperature.
但我无法找到我如何查询API简单地返回所有的城市,这将使我在我的列表视图,并允许用户看到的温度。
I hope this answers your query.
我希望这能解决你的疑问。
Thus, in due order I come to the interactive query for searches.
这样,按期望的次序开始进行检索的交互式查询。
In addition to query by content, I can look for images by metadata keywords, such as filename, description, and creation date.
除了按内容查询之外,还可以按元数据关键字,比如文件名、描述和创建日期来查找文件。
I can express the query as a rough sketch I paint or as another image I supply.
我可以将此查询表述为我所绘制的一个草图或我提供的另一个图像。
I often create a simple report rather than a work item query when I need to include information from many different sources.
当我需要包含来自许多不同来源的信息时,我通常会创建一个简单的报表,而不是一个工作项查询。
For the purposes of this discussion, I prefix all query names with the short (unqualified) name of the domain class.
出于讨论目的,我为所有查询名称都加了域类的短(非限定)名称作为前缀。
I think maybe it stands for query, but it's not documented.
我认为它也许代表查询,但是文档中没有说明。
But, you can certainly tell me if I described a database query wrong if I was using SQL.
而如果我使用SQL,那么你就可能直接告诉我某处数据库查询表述是否错了。
Because I allow both a method call and a property call to work as a definition query, I must write at least two tests in Listing 14.
因为我同时允许让方法调用和属性调用作为定义查询,因此在清单14中必须编写至少两个测试。
By that, I mean the query itself does not provide enough information for us to understand what the user is looking for.
因为有的时候通过一个简单的查询我们无法了解到用户真正想要的是什么。
If I could just change the query and restart, then I can test much quicker.
如果能够仅更改查询并重新启动,则可以更快地进行测试。
I can easily wrap the named query in a method and execute it again and again.
我可以方便地将命名查询打包在一个方法中,并重复执行它。
The 16 queries in the benchmark were based on real application query requests I have seen from business users.
基准测试程序中的16个查询基于我从企业用户那里看到的直实应用程序查询请求。
How do I recreate the same query access plan on my test environment that I am getting on my production environment?
我如何在接手生产环境的测试环境中重新创建相同的查询访问计划呢?
As I mentioned earlier, every query expression is generically typed to denote the type of the value the expression evaluates to.
如前所述,每个查询表达式都是泛型的,以表示表达式计算的值的类型。
But I am still left with my query: Why wait?
但我的疑问还在:为什么要等?
When I rerun the query from Listing 6, guess what's there?
当我从清单6返回查询时,猜猜是什么?
应用推荐