D
dbeavon
Guest
As I said, I accept that it is a client-side code is part of the problem as well. But in this case, "it takes two". The OE database server is just as much at fault for *allowing* a client connection to hold a transaction open for hours at a time. The server should have a way to enforce its own timeout as well. A database transaction timeout is not a new concept. It is a constraint that is enforced within the *database*, not by client program. That concept should not be conflated with features in the client-side programming (ie. things like "lock-wait" and "STOP-AFTER" that are basically features which control the execution-flow within an individual ABL client process).
Continue reading...
Continue reading...