Probably in the APL code with some support code in the library. The reason for this is that a native library can only have a single entry point, and that entry point has to be *either* an operator *or* a normal function. It's a normal function now, and I have no intention of changing that.
Regards, Elias On 21 April 2014 13:37, David B. Lamkins <dlamk...@gmail.com> wrote: > On Mon, 2014-04-21 at 12:21 +0800, Elias Mårtenson wrote: > > I think that I should probably implement SQL∆with_transaction. It > > belongs in the SQL layer. It's also the only way to ensure that > > transaction rollback on error is handled correctly. > > I agree that that's probably the right place to do it. Would it be in > the library (C) or in the wrapper (APL)? > > I kind of like the operator approach (as in the component file code), > but my implementation might not be sufficiently general for other > applications. > > >
