-
Notifications
You must be signed in to change notification settings - Fork 54
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
No callbacks are called #84
Comments
same here! |
@markstory I know you're not a fan of adding behavior support because some behaviors may be incompatible, but couldn't the same thing be said about a behavior targeting a specific database? For instance, I could write something that targeted a specific column type only available to postgres. I don't see why we can't put a big fat caveat on this plugin and say certain core behaviors are not expected to work (or make them work). |
Outside of the TimestampBehavior, I'm not sure any of the core behaviors work. |
Looks like we never implemented the default callback binding, for |
@markstory how difficult would it be to test that? Why do you think they wouldn't work? |
This lets the elasticsearch plugin work more like the ORM. Refs #84
Pull request up now. |
@josegonzalez I don't think the others would work based on how they are implemented. TreeBehavior, CounterCache and TranslateBehavior rely on association methods that do not exist in elasticsearch. |
Hi, I have this code in my controller:
This is my CompaniesType in plugin Companies:
Document is created and no callbacks are called
The text was updated successfully, but these errors were encountered: