EOQualifier (WebObjects 5.4.2 Reference)

Overview

Package

Class

Tree

Deprecated

Index

Help

WebObjects 5.4.2

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

com.webobjects.eocontrol
Class EOQualifier

java.lang.Object
  com.webobjects.eocontrol.EOQualifier

All Implemented Interfaces:: EOQualifierEvaluation, Serializable

Direct Known Subclasses:: BooleanQualifier, EOAndQualifier, EOKeyComparisonQualifier, EOKeyValueQualifier, EONotQualifier, EOOrQualifier, EOSQLQualifier, NonNullQualifier

public abstract class EOQualifier
extends Object
implements Serializable, EOQualifierEvaluation
extends Object
implements Serializable, EOQualifierEvaluation

EOQualifier is an abstract class for objects that hold information used to restrict selections on objects or database rows according to specified criteria. With the exception of EOSQLQualifier (EOAccess), qualifiers aren't based on SQL and they don't rely upon an EOModel (EOAccess). Thus, the same qualifier can be used both to perform in memory searches and to fetch from the database.

You never instantiate an instance of EOQualifier. Rather, you use one of its subclasses, your own custom EOQualifier subclasses, or one of the following classes:

Subclass Purpose

Subclass	Purpose
EOKeyValueQualifier	Compares the named property of an object to a supplied value, for example , "weight > 150".
EOKeyComparisonQualifier	Compares the named property of one object with the named property of another, for example "name = wife.name".
EOAndQualifier	Contains multiple qualifiers, which it conjoins. For example, "name = 'Fred' AND age < 20".
EOOrQualifier	Contains multiple qualifiers, which it disjoins. For example, "name = 'Fred' OR name = 'Ethel'".
EONotQualifier	Contains a single qualifier, which it negates. For example, " NOT (name = 'Fred')".
EOSQLQualifier	Contains unstructured text that can be transformed into a SQL expression. EOSQLQualifier provides a way to create SQL expressions with any arbitrary SQL. Because EOSQLQualifiers can't be evaluated against objects in memory and because they contain database and SQL specific content, you should use EOQualifier wherever possible.

The interface EOQualifierEvaluation defines how qualifiers are evaluated in memory. To evaluate qualifiers in a database, methods in EOSQLExpression (EOAccess) and EOEntity (EOAccess) are used to generate SQL for qualifiers. Note that all of the SQL generation functionality is contained in the access layer.

Creating a Qualifier

As described above, there are several EOQualifier subclasses, each of which represents a different semantic. However, in most cases you simply create a qualifier using the EOQualifier static method qualifierWithQualifierFormat , as follows:

 EOQualifier    qual    = EOQualifier.qualifierWithQualifierFormat("lastName = 'Smith'", null);

The qualifier or group of qualifiers that result from such a statement is based on the contents of the format string you provide. For example, giving the format string "lastName = 'Smith'" as an argument to qualifierWithQualifierFormat returns an EOKeyValueQualifier object. But you don't normally need to be concerned with this level of detail.

The format strings you use to create a qualifier can be compound logical expressions, such as "firstName = 'Fred' AND age < 20" . When you create a qualifier, compound logical expressions are translated into a tree of EOQualifier nodes. Logical operators such as AND and OR become EOAndQualifiers and EOOrQualifiers, respectively. These qualifiers conjoin (AND) or disjoin (OR) a group of sub qualifiers.

Constructing Format Strings

As described above, you typically create a qualifier from a format string by using qualifierWithQualifierFormat. This method takes as an argument a format string vaguely similar to the standard C printf() function. The format string can embed strings, numbers, and other objects using the conversion specification %@. The second argument to qualifierWithQualifierFormat is an array that contains the value or result to substitute for any %@ conversion specifications. This allows qualifiers to be built dynamically. The following table lists the conversion specifications you can use in a format string and their corresponding data types.

Conversion Specification	Expected Value or Result
%s	A String object, or the result of the `toString` method
%d	An Integer or something which can be converted into an Integer.
%f	A Double or something which can be converted into a Double
%@	An arbitrary Object argument. No conversions are performed.
%K	Similar to %@ except the argument is coerced to a String with `toString` and treated as a key which can determine whether the resultant qualifier is an EOKeyValueQualifier or an EOKeyComparisonQualifer.
%%	Results in a literal % character.

If you use an unrecognized character in a conversion specification (for example, %x), an exception is thrown.

For example, suppose you have an Employee entity with the properties empID, firstName, lastName, salary, and department (representing a to-one relationship to the employee's department), and a Department entity with properties deptID, and name. You could construct simple qualifier strings like the following:

          lastName = 'Smith'
          salary > 2500
          department.name = 'Personnel'

The following examples build qualifiers similar to the qualifier strings described above, but take the specific values from already fetched enterprise objects:

 Employee anEmployee; // Assume this exists.
 Department aDept; // Assume this exists.
 EOQualifier myQualifier;
 NSMutableArray args = new MutableVector();
 args.addObject("lastName");
 args.addObject(anEmployee.lastName());
 myQualifier = EOQualifier.qualifierWithQualifierFormat("%@ = %@", args);
 args.removeAllObjects();
 args.addObject("salary");
 args.addObject(anEmployee.salary());
 myQualifier = EOQualifier.qualifierWithQualifierFormat("%@ > %f", args);
 args.removeAllElements();
 args.addElement("department.name");
 args.addElement(aDept.name());
 myQualifier = EOQualifier.qualifierWithQualifierFormat("%@ = %@", args);

The enterprise objects here implement methods for directly accessing the given attributes: lastName and salary for Employee objects, and name for Department objects. Note that unlike a string literal, the %@ conversion specification is never surrounded by single quotes:

 // For a literal string value such as Smith, you use single quotes.
 EOQualifier.qualifierWithQualifierFormat("lastName = 'Smith'", null);
 // For the conversion specification %@, you don't use quotes
 args.removeAllElements();
 args.addElement("Jones");
 EOQualifier.qualifierWithQualifierFormat("lastName = %@", args);

Typically format strings include only two data types: strings and numbers. Single quoted or double quoted strings correspond to String objects in the argument array, non quoted numbers correspond to Numbers, and non quoted strings are keys. You can get around this limitation by performing explicit casting.

The operators you can use in constructing qualifiers are =, ==, !=, <, >, <=, >=, "like", and "caseInsensitiveLike". The like and caseInsensitiveLike operators can be used with wildcards to perform pattern matching,

Checking for NULL Values

To construct a qualifier that fetches rows matching NULL, you can use either of the approaches shown in the following example:

 NSMutableArray args = new NSMutableArray();
 // Approach 1
 EOQualifier.qualifierWithQualifierFormat("bonus = nil", null);
 // Approach 2
 args.addElement(NullValue.nullValue());
 EOQualifier.qualifierWithQualifierFormat("bonus = %@", args);

Using Wildcards and the like Operator

When you use the like or caseInsensitiveLike operator in a qualifier expression, you can use the wildcard characters * and ? to perform pattern matching, for example:

 "lastName like 'Jo*'"

matches Jones, Johnson, Jolsen, Josephs, and so on.

The ? character just matches a single character, for example:

 "lastName like 'Jone?'"

matches Jones.

The asterisk character ( ) is only interpreted as a wildcard in expressions that use the like or caseInsensitiveLike operator. For example, in the following statement, the character * is treated as a literal value, not as a wildcard:

          quot;lastName = 'Jo*'"

Using Selectors in Qualifier Expressions

The format strings you use to initialize a qualifier can include methods. The parser recognizes an unquoted string followed by a colon (such as myMethod: ) as a method. For example:

          point1 isInside: area
          firstName isAnagramOfString: "Computer"

The method signature of the embedded selector (isAnagramOfString in this example must be:

 public Boolean isAnagramOfString(String aString) {}

You can also pass an Object rather than a String. If you pass an Object, the invocation is wrapped in an exception handler and returns false unless you return a Boolean.

Methods specified in a qualifier are parsed and applied only in memory; that is, they can't be used in to qualify fetches in a database.

Using EOQualifier's Subclasses

You rarely need to explicitly create an instance of EOAndQualifier, EOOrQualifier, or EONotQualifier. However, you may want to create instances of EOKeyValueQualifier and EOKeyComparisionQualifier. The primary advantage of this is that it lets you exercise more control over how the qualifier is constructed.

If you want to explicitly create a qualifier subclass, you can do it using code such as the following excerpt, which uses EOKeyValueQualifier to select all objects whose "isOut" key is equal to 1 (meaning true). In the excerpt, the qualifier is used to filter an in memory array.

 // Create the qualifier
 EOQualifier qual = new EOKeyValueQualifier("isOut", EOQualifier.QualifierOperatorEqual, new Integer(1));
 // Filter an array and return it
 return Qualifier.filteredVectorWithQualifier(allRentals(), qual);

filteredArrayWithQualifier is a method that returns an array containing objects from the provided array that match the provided qualifier.

Creating Subclasses

A custom subclass of EOQualifier must implement the EOQualifierEvaluation interface if they are to be evaluated in memory.

See Also:: Serialized Form

Nested Class Summary
`static interface`	`EOQualifier.Comparison` The EOQualifierComparison interface defines methods for comparing values.
`static class`	`EOQualifier.ComparisonSupport` The Java Client EOQualifier.ComparisonSupport class provides default implementations of the EOQualifierComparison interface.
`class`	`EOQualifier.QualifierVariableSubstitutionException`

Field Summary
`static NSSelector`	`QualifierOperatorCaseInsensitiveLike` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorContains` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorEqual` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorGreaterThan` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorGreaterThanOrEqualTo` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorLessThan` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorLessThanOrEqualTo` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorLike` One of the possible values of selector.
`static NSSelector`	`QualifierOperatorNotEqual` One of the possible values of selector.

Constructor Summary
`EOQualifier()`

Method Summary
`abstract void`	`addQualifierKeysToSet(NSMutableSet qualifierKeys)` Adds the receiver's qualifier keys to qualifierKeys.
`NSSet`	`allQualifierKeys()` Returns an NSSet of strings, which are the left hand sides of all the qualifiers in the receiver.
`static NSArray`	`allQualifierOperators()` Returns an NSArray containing all of the operators supported by EOQualifier.
`NSArray`	`bindingKeys()` Returns an array of strings which are the names of the known variables.
`Object`	`clone()` Returns an exact replica of the receiver.
`boolean`	`evaluateWithObject(Object object)` Implemented by subclasses to return `true` if object matches the criteria specified in the receiver, `false` otherwise.
`static void`	`filterArrayWithQualifier(NSMutableArray array, EOQualifier qualifier)` Filters array in place so that it contains only objects matching qualifier.
`static NSArray`	`filteredArrayWithQualifier(NSArray array, EOQualifier qualifier)` Returns a new array that contains only the array from objects matching qualifier.
`String`	`keyPathForBindingKey(String key)` Returns a string which is the left hand side of the variable in the qualifier.
`protected static NSSelector`	`operatorSelectorForSelectorNamed(String string)` Returns a named operator selector.
`static NSSelector`	`operatorSelectorForString(String string)` Returns an operator selector based on the string string.
`static EOQualifier`	`qualifierToMatchAllValues(NSDictionary values)` Takes a dictionary of search criteria, from which the method creates EOKeyValueQualifiers (one for each dictionary entry).
`static EOQualifier`	`qualifierToMatchAnyValue(NSDictionary values)` Takes a dictionary of search criteria, from which the method creates EOKeyValueQualifiers (one for each dictionary entry).
`abstract EOQualifier`	`qualifierWithBindings(NSDictionary bindings, boolean requiresAll)` Returns a new qualifier substituting all variables with values found in bindings.
`static EOQualifier`	`qualifierWithQualifierFormat(String format, NSArray arguments)` Parses the format string format and the specified arguments, uses them to create an EOQualifier, and returns the EOQualifier.
`static NSArray`	`relationalQualifierOperators()` Returns an NSArray containing all of the relational operators supported by EOQualifier.
`static String`	`stringForOperatorSelector(NSSelector selector)` Returns a string representation of the selector selector.
`abstract void`	`validateKeysWithRootClassDescription(EOClassDescription classDescription)` Ensures that the receiver contains keys and key paths that belong to or originate from classDescription.

Methods inherited from class java.lang.Object
`equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait`

Field Detail