Problems with triggers and TDDDMonitoredDaemonProcessRest

fabiovip2019 · 2021-07-08 15:31:55

Hi everyone, I'm using the TDDDMonitoredDaemonProcessRest class to monitor some update states within the system. This monitoring takes place on a field changed via trigger directly in the database. The problem is that orm only recognizes the changes when I start the server, then all subsequent changes are not recognized by orm.
Is there any kind of refresh from TSQLRecord?
See the code excerpt below:

function TProductDaemonProcess.ExecuteRetrievePendingAndSetProcessing: boolean;
begin
   fPendingTask := (fDaemon as TSyncProdutoIntegraDaemon).RestClass.Create(
   fDaemon.Rest,'IdWooCommerce>0 and (SyncSupraWoo=? or SyncSupraWoo is null)',['N']);
  if fPendingTask.ID=0 then begin
    result := false; 
    exit;
  end;
end;

ab · 2021-07-09 07:39:49

I really don't understand what you mean.

Can you detail what "monitor some update stats within the system"?
(please use gist to post some code)

fabiovip2019 · 2021-07-09 11:53:34

Hi, Ab

The TDDDMonitoredDaemonProcessRest class serves to monitor the state of some field in a table and perform an action on the value contained in this field, right?
When the change in the value of this field being monitored occurs via trigger directly in the database, this change is not seen by TSQLRecord.
This way, when this SyncSupraWoo field is receiving a value directly from a trigger in the database, fPendingTask is never created. Understood?

fabiovip2019 · 2021-07-09 18:06:06

Has anyone ever experienced this?

ab · 2021-07-09 18:49:12

TDDDMonitoredDaemonProcessRest has nothing to do directly about "monitoring the state of some field in a table".

It is about running some background process, with start/stop and state abilities.

fabiovip2019 · 2021-07-09 18:58:07

hi ab,
Maybe I expressed myself wrongly. When I say monitor I am referring to the ExecuteRetrievePendingAndSetProcessing method which is checking the value of a given field to return true or false. that's the concept of pendingtask isn't it? or am I mistaken?

ab · 2021-07-09 20:27:06

Your TProductDaemonProcess.ExecuteRetrievePendingAndSetProcessing returns false in the last then begin...end but leave result unset.
It should return true or false.

The global logic is in TDDDMonitoredDaemonProcess.Execute.

One example of use is TDDDEmailerDaemonProcess.

fabiovip2019 · 2021-07-12 11:43:19

That's right Ab, in TDDDEmailerDaemonProcess who the method's True or False result is controlled according to the value of TSQLRecord's State field.

fPendingTask := (fDaemon as TDDDEmailerDaemon).RestClass.Create(
    fDaemon.Rest,'State=? order by RowID',[ord(esPending)]);

that's exactly what doesn't work in my case, when the value of this field is changed by a trigger in the Bank a some manual update.
TSQLRecord in my case doesn't recognize that the field value has changed, so the method never returns True.

fabiovip2019 · 2021-07-12 12:36:11

Hi Ab, I found out that the problem is related to my mounted where clause.
It does not work:
IdWooCommerce>0 and (SyncSupraWoo=? or SyncSupraWoo is null)

but it works:

SyncSupraWoo=? or SyncSupraWoo is null

I can't use clause and with or.

mORMot Open Source

#1 2021-07-08 15:31:55

Problems with triggers and TDDDMonitoredDaemonProcessRest

#2 2021-07-09 07:39:49

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#3 2021-07-09 11:53:34

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#4 2021-07-09 18:06:06

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#5 2021-07-09 18:49:12

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#6 2021-07-09 18:58:07

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#7 2021-07-09 20:27:06

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#8 2021-07-12 11:43:19

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

#9 2021-07-12 12:36:11

Re: Problems with triggers and TDDDMonitoredDaemonProcessRest

Board footer