Add support for stored procedures in persistence

Needed to support new functionality for reports in membership. Stored procedures were chosen to remove direct/raw SQL writing from Java APIs, and to enable us to add parameters to what amounts to a view. This was the best way to accomplish this.

requested review from @mbarbero, @heurtemattes, and @zacharysabourin

Additionally, no tests were written as support in H2 (our test DB, as it can be in memory) for stored procedures looks to be radically different from how it is done in MariaDB. Hopefully in the future I can spend more time on this and create debt items to address missing testing in the framework

added 4 commits

• d2bca1b4...06b4a6a5 - 3 commits from branch master
• df7bac57 - Add support for stored procedures in persistence

Compare with previous version

@heurtemattes as everyone is at ECon next week can you review this on Monday? This is blocking some stuff downstream and needs to be merged in, and I'd rather some bigger stuff be at least vetted by people that aren't me haha

Not a big fan of Stored procedures. Usually I don't recommended to use them. I'm sure you have the right use case.

Note, that you change your formatter! many lines has been modified.

approved this merge request

I switched back to eclipse from VS Code since I've had nothing but problems with it. While it technically used the same formatting rules it ended up a little different.

We're using a stored procedure as we need a virtual table, MariaDB views don't support variables, and we would otherwise need a virtual table made in Hibernate which has been kind of janky in my experience. Procedures can do what views do and take variables as well, so it fit for our use case

added 3 commits

• df7bac57...2de83c39 - 2 commits from branch master
• 4afe4deb - Add support for stored procedures in persistence

Compare with previous version

merged