You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several of the stub methods in JdbcInsert don't call the next interceptor in the chain, effectively making JdbcInsert a dead end for those methods. For example, postSearchEntry and postSearchComplete. Is that a bug, or is it intentional for some reason that I don't grok?
FWIW, I'm trying to work around issue #82, and I finally discovered why my insert isn't getting invoked after JdbcInsert.
The text was updated successfully, but these errors were encountered:
I wanted to have an insert modify binary attributes, and I had wrongly assumed they were not available until after the JdbcInsert had done its thing. But I see now that all of the accumulated LDAPattributes are present in postSearchEntry() when I put my insert before JdbcInsert. Other than that, it was mostly curiosity that made me ask after I noticed it.
Feel free to close the issue if it's ... not an issue. :-)
MyVD 1.0.6.
Several of the stub methods in JdbcInsert don't call the next interceptor in the chain, effectively making JdbcInsert a dead end for those methods. For example, postSearchEntry and postSearchComplete. Is that a bug, or is it intentional for some reason that I don't grok?
FWIW, I'm trying to work around issue #82, and I finally discovered why my insert isn't getting invoked after JdbcInsert.
The text was updated successfully, but these errors were encountered: