Is there a way of saying "only import the new stuff" (eg the same primary key) or ignoring when there is a clash?

Roy Lambert

Roy, the way I do it, is I have a key, like you suggested, and then I trap
the error:
   try
     execute query here
   except
     on E: EDatabaseError do
     begin
       sError := lowercase(E.Message);
       // some other error trapping here
       end
       else if (    (pos('duplicate',sError) > 0)
                 or (pos('1004',sError) > 0)
               ) then // error updating/adding with a primary key
       begin
           // do nothing, this is okay.
       end;
    end;
 end;

Daniel


Does that way simply halt the import with a user message or allow it to continue adding new data?

Roy Lambert

Roy,

<< Is there a way of saying "only import the new stuff" (eg the same primary
key) or ignoring when there is a clash? >>

You can use an ON ERROR trigger to eat such exceptions.  Just create it
before the import, and then drop it afterwards, or leave it created and make
sure to disable it for normal operation.  Just an empty trigger will do the
trick:

CREATE TRIGGER "ImportError" ERROR INSERT
ON "MyTable"
BEGIN
END

You could also use it to log the rows with errors to a different log/audit
table.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Hmm, interesting, and yet another of those cases where its "all off and damn well stay off"

Roy Lambert

Roy:
Since it catches the exception, it contiues importing. You may want to use
Tim's idea with the trigger instead.

Daniel