These addItemToCollectionOperation and removeItemFromCollectionOperation are optional operations which let you define a function to be invoked as an item is added to or removed from a collection. In many cases, the membership of items in the query is determined implicitly - i.e. by the property values so the server does not need to handle these operations. In those cases, they are ignored. Use these methods in case you are explicitly managing an association table which relates the item to a particular collection.

Name of an operation on the service taking the same parameters as this operation which returns the number of items in the query. Use this if you enable paging to get the accurate collection size. If you don't define a count operation, the system uses a dynamic sizing mode which fetches the items in the collection one page at a time leaving an empty slot at the end. If you do not access that empty slot, the next page is not fetched. When you do access that slot, the next page is fetched and the collection size is increased until there are no more remaining items in the query.

Page size for this query when paging is enabled.

Set this to true to enable paging. When paging is enabled, your operation on the server must take a start and count parameters to define the subset of the items to return. You do not provide these to the service when you call the operation - they are added automatically as the system will fetch pages from your server on-demand - i.e. in response to getItemAt calls. Those calls take an optional prefetch parameter which lets you control the number of items fetched on a given call.

When paging is enabled, your operation on the server must take a start and count parameters to define the subset of the items to return. You do not provide these to the service when you call the operation - they are added automatically as the system will fetch pages from your server on-demand - i.e. in response to getItemAt calls. Those calls take an optional prefetch parameter which lets you control the number of items fetched on a given call. By default the start and count parameters must be called "startIndex" and "numItems" and may appear anywhere in the signature of your operation. Setting this flag to true will lift the naming restriction on these two parameters, but will require that they appear as the last two parameters to the operation - the second to last parameter will be interpreted as the start parameter and the last as the count parameter.

A string of the form "a,b,c" which lists the property names of the managed item returned by this query. If unset, the query should return all properties of the object.

These addItemToCollectionOperation and removeItemFromCollectionOperation are optional operations which let you define a function to be invoked as an item is added to or removed from a collection. In many cases, the membership of items in the query is determined implicitly - i.e. by the property values so the server does not need to handle these operations. In those cases, they are ignored. Use these methods in case you are explicitly managing an association table which relates the item to a particular collection. When an item is removed from a collection, if you want to delete that item, you do not need to use this operation. Instead, set the property deleteItemOnRemoveFromFill and the server's deleteItem operation is called automatically when the item is removed from the collection. .

Builds a ManagedQuery. The nameParameter specifies the name of the service's operation which this ManagedQuery is based off of. It is a required parameter but is made optional here so this class can be used in MXML.

Initializes the managed operation throwing errors for any configuration problems that are encountered along the way.