RE: Fitzle

> From: furgalj@xxxxxxxxxxxxxxxx
> 
> Well as always, the code is what really does the work, so maybe he
could
> post sample. But my guess is that he has sets of SQL INSERT and UPDATE
> statements in JDBC calls. Then these are bracketed by commits or
> rollbacks.

No, because according to Dieter these are all in one large transaction.
That in fact was the point of his argument; by combining all this stuff
into one transaction, he insists that you can even see performance
BENEFITS from CC.


> BTW, maybe the language you were thinking of was Prologue, instead of
> lisp? This was non-procedural. You just specified a set of rules and
the
> conditions that caused them to fire. But I believe the
prologue/epilogue
> sections (if I'm remembering this right) did allow for procedural code
for
> housekeeping and error handling.

Yup, I think this was it.  The language was embedded in a MIDI
controller application, and was used to transform the MIDI stream based
on rules.

Joe