D
dbeavon
Guest
True, but you point out that it doesn't always work reliably, even for purposes that have nothing to do with the database (eg to interrupt external interfaces). That is the reason that the database needs a "backup plan". ... so if a user session locks a record in the database, and then that session gets held up by some external interface that is outside the control of the 4GL runtime, then that record will remain locked even after the stop-after timeout has expired. That is why the database server needs its own timeout - so that it can eventually release those locked records one way or another. Otherwise there is a potential concurrency problem that could grow out of hand (sessions will start piling up). IMHO the database server should be able to protect its own interests, and should NOT be at the mercy of some misbehaving 4GL session that runs on some remote PASOE server somewhere. This is analogous to a "DBA-administrator-bot" that would disconnect remote connections after a predetermined amount of time has elapsed.
Continue reading...
Continue reading...