Do Not Make This Mistake When Developing an SPI | Java, SQL and jOOQ.
Most of your code is private, internal, proprietary, and will never be exposed to public. If that's the case, you can relax – you can refactor all of your mistakes, including those that incur breaking API changes.
If you're maintining public API, however, that's not the case. If you're maintaining public SPI (Service Provider Interfaces), then things get even worse.
The H2 Trigger SPI
In a recent Stack Overflow question about how to implement an H2 database trigger with jOOQ, I have encountered the org.h2.api.Trigger SPI again – a simple and easy-to-implement SPI that implements trigger semantics. Here's how triggers work in the H2 database:
Read full article from Do Not Make This Mistake When Developing an SPI | Java, SQL and jOOQ.
No comments:
Post a Comment