zipcode

Observant readers might notice that the zipCode field is a normal text field .

细心的读者可能注意到zipCode是一个普通的文本字段。

Below is an example of a custom constraint named ZipCode

如下代码自定义了一个名为ZipCode的约束

Therefore , it can use Partition 1 of our index the traditional way to avoid a sort on ZIPCODE .

因此，它可以以传统方法使用我们索引的Partition1来避免在ZIPCODE上进行排序。

Alter domain zipcode set schema customers .

把域移动到另外一个模式。

You can specify the @ ZipCode constraint on a class , field , or property just like any other constraint .

可以将@ZipCode用在类、属性或是方法上，就像其他约束一样。

Alter domain zipcode drop not null ;

从一个域里删除一个；

Even though LASTNAME is not part of our ZIPCODE index , DB2 knows that the rows we want can only be in Partition 1 .

尽管LASTNAME是我们的ZIPCODE索引的not部分，但是DB2知道我们想要的行可能只是在Partition1中。

The XML from the client uses a zipCode element , while the server expects the zip code to be in a zip-code element .

来自客户机的XML使用了zipCode元素，而服务器希望邮政编码放在zip-code元素中。

The weather service requires you to call the getTempRequest method by passing in a zipcode value as a string and receiving the temperature as a floating-point value in the response .

传递一个zipcode字符串值给天气信息服务的getTempRequest方法调用，最后以接收到的浮点值温度作为响应。

Because the NPSI is a single ordered list , it is easy to see how DB2 could just toggle back and forth , index to table , index to table , and return rows in ZIPCODE order without sorting .

因为NPSI是一个单序列列表，很容易看到DB2如何来回切换，从表到索引、索引到表，然后以ZIPCODE次序返回行，而不需要排序。

It still has issues : Zipcode is enough to identify the city and state , so those attributes should migrate to a City table ( instead of a state table ), but that data is static , so we 'll leave it alone .

它还有问题：Zipcode已足够识别国家与城市，因此，这些属性应当被迁移到City表（而不是状态表），但是该数据是静态的，因此我们可以不必理会。

For example , the Arabic numeral recognition system , only carries on the recognition to Arabic numeral , is applied in so many domain , such as zipcode recognition , the license plate recognition , product serial number recognition on assembly line , etc.

如阿拉伯数字识别系统，仅对10个阿拉伯数字和少量符号进行识别，可以广泛应用于邮政编码识别、汽车牌照识别，流水线上产品编号识别等领域。

If the relation is eager or navigated from the non-owning side or a query that requires join such as'select p from Person p where p.address . zipcode = 12345 ' , it will produce an erroneous result .

如果关系是迫切需要的或从非拥有侧导航来的或者是要求类似像'selectpfromPersonpwherep.address.zipcode=12345'这样的连接的一个查询，那么它将生成一个错误结果。

While the first question may seem downright daft , a box pops up allowing users in input their postcode or zipcode , to help them with their journey , but unfortunately the search engine is not able to beat Nasa in its quest to find alien life , which it hopes to do before 2025 .

尽管前一个问题可能看起来蠢透了，但有个窗口会跳出来，让用户输入他们家的邮政编码，帮助他们回家。只可惜在寻找外星生命方面，搜索引擎无法超越美国太空总署，而后者希望在2025年之前发现外星生命。