Hello omc2016. I apologize for the long delay in response. I'm on holiday this week and have a chance to look at this.

The trigger feature does look poorly documented, as if I never got around to building it out properly. I would think it works though, as there is an example and unit test.

I see one example, SingleTableTrigger. The unit test is next to it. Theres a triggers.properties in the resources area of test that sets it up. Probably there is one impl class per table. The table is declared as SingleTable in the resources/xml/sqlresources. It's sakila.actor. I can see the trigger's beforeInsert/Update throw a InvalidRequestException and it's expected in the unit test.

Running the test suite is essential to building your confidence in the change / addition. There's the README.txt for an overview. You'll have to set up the sakila database, a sample from the mysql community project. And you'll have to install the java build tool ant (now eclipsed by maven, gradle, etc.). Ant uses build.xml. Run ant -p verbose to list all targets (actions).

But really the place to get started is the framework developers guide. That describes all the prereqs and tooling.

Good luck!

Mark

restSQL on Tomcat 9 #89

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions