When uniQuery is opened, why DataSource.onDataChange trigger 2 times?

Question

I've a question about unidac's uniQuery:

when uniQuery open, if a DataSource component is linked, the DataSource.onDataChange will trigger 2 times, and ADOQuery trigger just 1 time, why?

Environment:

uniDAC：6.4, 7;
delphi: 7, xe 10.1 berlin

If you want to add details to your question, do so by editing the question (see the `edit` button below the tags) — Tom Brunberg, Aug 30 '17 at 06:26
i'v already tested 2 kind of table: 1. only 1 record 2. more than 10 thousands records and different "uniQuery.fetchrows" no different — d5f, Aug 30 '17 at 12:52

score 0 · Answer 1 · answered Aug 30 '17 at 14:01

I faced the same problem many times, I found that it is a default loading behavior not just in the Uni-component, all similar database components will trigger .onDataChange twice or more when loading, the only way to go over it is by using workarounds to ignore the 1st trigger.

You can find also a similar problem here

If triggering twice is annoying you, try my workaround for it:

var c: integer;  // must be global and reset to 0 when u close your query  

procedure TForm1.DataSource1DataChange(Sender: TObject; Field: TField);
    begin
      if c = 2 then
        begin
          // do your actions
        end
      else
        begin
          inc(c);
        end;
    end;

It will eliminate all none necessary triggers,
hope that helps.

When uniQuery is opened, why DataSource.onDataChange trigger 2 times?

1 Answers1