Programming Filter Function Actions
Go Up to Writing an External Blob Filter
When an application invokes a Blob API function on a Blob to be filtered, InterBase passes a corresponding action message to the filter function by way of the action parameter. There are eight possible actions. The following action macro definitions are declared in the ibase.h file:
|
|
0 |
|
|
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
6 |
|
|
7 |
The following table lists the actions, and specifies when the filter function is invoked with each particular action. Most of the actions are the result of events that occur when an application invokes a Blob API function.
| Action | When filter is invoked with corresponding action |
|---|---|
|
|
Invoked when an application calls |
|
|
Invoked when an application calls |
|
|
Invoked when an application calls |
|
|
Invoked when an application calls |
|
|
Invoked when an application calls |
|
|
Invoked when InterBase initializes filter processing; not a result of a particular application action. |
|
|
Invoked when InterBase ends filter processing; not a result of a particular application action. |
|
|
Reserved for internal filter use; not used by external filters. |
This concludes the overview of writing Blob filters. For detailed information about filters and how to program filter function actions, as well as a reference to a filter application example, see the Embedded SQL Guide.