mirror of
https://github.com/google/nomulus.git
synced 2025-06-16 09:24:47 +02:00
52fd9d8c4e
Usually, the correct order happens automatically, because we are searching on either the key or a specific field like fullyQualifiedDomainName, and the results come back in that order. But when searching by nameserver, where we split the query into multiple "IN" chunks, we have to assemble the result set and order after the fact. The tests didn't pick up the problem, because the domains and hosts were created in alphabetical order, so it happened to work anyway. The tests have now been changed to create things in reverse order, to test the reordering. Also, the previous arbitrary limit of 1000 nameservers in the intermediate query has been reduced to 300, because we now loop through all nameservers no matter what, rather than stopping when we collect enough domains, so there's more of a penalty for having way too many nameservers. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=173163121 |
||
|---|---|---|
| .. | ||
| BUILD | ||
| RdapActionBase.java | ||
| RdapAuthorization.java | ||
| RdapAutnumAction.java | ||
| RdapDomainAction.java | ||
| RdapDomainSearchAction.java | ||
| RdapEntityAction.java | ||
| RdapEntitySearchAction.java | ||
| RdapHelpAction.java | ||
| RdapIcannStandardInformation.java | ||
| RdapIpAction.java | ||
| RdapJsonFormatter.java | ||
| RdapModule.java | ||
| RdapNameserverAction.java | ||
| RdapNameserverSearchAction.java | ||
| RdapResourcesAndIncompletenessWarningType.java | ||
| RdapSearchPattern.java | ||
| RdapSearchResults.java | ||
| RdapUtils.java | ||