You can either get a simple static ContentResultSet or you can
listen to change-notifications and than swap from the old to a new
ContentResultSet.
The following describes the dynamic use:
XDynamicResultSet provides the possibility to get notifications
about changes on a ContentResultSet and have an
listener-controlled update from one version to the next version. Two
ContentResultSet implementations were given to the listener in
the first notification as interface
::com::sun::star::sdbc::XResultSet.
After registration you will get notifications for events of type
ListEvent.
The calling of XDynamicResultSetListener::notify has
to happen in an own thread, because it could take a longer time and any
actions til the listener returns the call. So don't block the notify-causing
action.
While one notify-call is going on:
The listener is allowed to access both ContentResultSets,
they must be both valid.
It is not allowed to start a second notify-call.
All addditional things we want to send as notification are to be
queued.
Any other calls are to be accepted and treated.
After the listener has returned the notify-call:
The listener is allowed to access the new
ContentResultSet. The new one is first assigned in the
WELCOME-event and than the ResultSets are always swapped.
Using this method you can get information, whether the offered
ContentResultSets are sorted or filtered etc correctly as
demanded during the creation of the XDynamicResultSet.
ListenerAlreadySetException
if this method is called more than once during the life of the
implementation object or if this method is called if someone already
has fetched the ContentResultSet via
XDynamicResultSet::getStaticResultSet.
Using this method you can get information, whether the offered
ContentResultSets are sorted or filtered etc correctly as
demanded during the creation of the XDynamicResultSet.
