Re: Fitzle

[furgalj@xxxxxxxxxxxxxxxx]

>Yeah, but this is where I get confused.  According to Dieter's posts,
>he's explicitly specifying the order of updates, which is how he reduces
>certain commitment control locking problems.
>
>I can understand your position on queries.  The system figures out what
>to do.  But this whole update process makes me crazy...
>
>Joe

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.

So yes, each individual SQL statement is non-procedural, but they are 
being issued in a particular sequence by the Java code.

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.

_________________________________________________________________
Jeff Furgal / MIMIX User Interface Product Architect / Lakeview Technology

furgalj@xxxxxxxxxxxxxxxx / 630-282-8360

LAKEVIEW TECHNOLOGY CONFIDENTIAL

This e-mail may contain SECRET, PRIVILEGED AND/OR CONFIDENTIAL INFORMATION 
intended only for the use of the addressee.  If you are not the addressee, 
or the person responsible for delivering it to the person addressed, you 
may not copy or deliver this to anyone else.  If you received this e-mail 
in error, please immediately notify Lakeview by returning the original 
message to the sender via e-mail.