There are actually two issues sitting here:
1. Transaction Recovery and
2. Knowing when you've lost a connection and when to restart it.
I am not familiar with PostgreSQL but with a transaction oriented
database such as Firebird or Oracle, when you lose a connection,
re-connecting doesn't als
On 12/11/17 09:30, Graeme Geldenhuys wrote:
On 2017-11-11 18:41, Mark Morgan Lloyd wrote:> the FPC/Lazarus controls
do a good job of presenting a common API> irrespective of what backend
server is being used, would it be feasible> to have a "reconnect
monitor" or similar to help recover from th
On 2017-11-12 01:27, James Richters wrote:
ClockBuffer_With_Time:=ClockBuffer_original;
That seems fine.
AggClockbuffer^:=ClockBuffer_With_Time^+3*Sizeof(Longint); //Set
AggClockBuffer to be 3 Longints past ClockBuffer_with_time
This seems wrong. Try changing that to the followin
On 2017-11-11 18:41, Mark Morgan Lloyd wrote:
the FPC/Lazarus controls do a good job of presenting a common API
irrespective of what backend server is being used, would it be feasible
to have a "reconnect monitor" or similar to help recover from this sort
of thing?
You should always program you
