public final class SortConditions extends BaseSearchConditions
Provides the search conditions for the SORT extension. Compatibles with SORT IMAP extension described at https://tools.ietf.org/html/rfc5256
Constructor and Description |
---|
SortConditions() |
Modifier and Type | Method and Description |
---|---|
int |
getReverseBy()
Gets or sets reverse sort criteria
Followed by another sort criterion, has the effect of that criterion but in reverse(descending) order.
|
int |
getSortBy()
Gets or sets sort criteria
|
void |
setReverseBy(int value)
Gets or sets reverse sort criteria
Followed by another sort criterion, has the effect of that criterion but in reverse(descending) order.
|
void |
setSortBy(int value)
Gets or sets sort criteria
|
getCharset, getSince, getText, getUseUId, setCharset, setSince, setText, setUseUId
public final int getSortBy()
Gets or sets sort criteria
public final void setSortBy(int value)
Gets or sets sort criteria
public final int getReverseBy()
Gets or sets reverse sort criteria Followed by another sort criterion, has the effect of that criterion but in reverse(descending) order. Note: REVERSE only reverses a single criterion, and does not affect the implicit "sequence number" sort criterion if all other criteria are identical. Consequently, a sort of REVERSE SUBJECT is not the same as a reverse ordering of a SUBJECT sort. This can be avoided by use of additional criteria, e.g., SUBJECT DATE vs. REVERSE SUBJECT REVERSE DATE. In general, however, it's better (and faster, if the client has a "reverse current ordering" command) to reverse the results in the client instead of issuing a new SORT.
public final void setReverseBy(int value)
Gets or sets reverse sort criteria Followed by another sort criterion, has the effect of that criterion but in reverse(descending) order. Note: REVERSE only reverses a single criterion, and does not affect the implicit "sequence number" sort criterion if all other criteria are identical. Consequently, a sort of REVERSE SUBJECT is not the same as a reverse ordering of a SUBJECT sort. This can be avoided by use of additional criteria, e.g., SUBJECT DATE vs. REVERSE SUBJECT REVERSE DATE. In general, however, it's better (and faster, if the client has a "reverse current ordering" command) to reverse the results in the client instead of issuing a new SORT.
Copyright (c) 2008-2022 Aspose Pty Ltd. All Rights Reserved.