Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hooks and Callbacks [moved] #38

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Hooks and Callbacks [moved] #38

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 38 moved from a Google Code project.
Added by 2010-05-25T21:15:13.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-High, v0.9.16

Original description

Before to design the trigger API OrientDB needs to expose internal
callbacks and hooks via APIs.

In this way the user application can:
 * to handle cascade events, such as after a deletion
 * to update an external index, such as Lucene (anyone is interested in the
support of it?)
 * to monitor events
 * write something like homebrew triggers waiting for the official API
@lvca lvca closed this as completed Dec 10, 2012
lvca added a commit that referenced this issue Oct 15, 2015
@ghost ghost mentioned this issue Nov 3, 2016
4 tasks
tglman pushed a commit that referenced this issue Feb 21, 2024
tglman added a commit that referenced this issue Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant