You're welcome! What comes to that thing with that update, it is a build in feature since setting up that kind of update logic would be far more complex than this insertion logic. Now I image that this is just using some type of SQL query on the background to get values that have been added/changed after the previous run like this: SELECT col1 ,col2 FROM source WHERE col2 > saved_value_for_col2 -> Then this logic will just insert the rows that result from this query and save the largest value for col2 for the next run. --> That update logic (and also delete) logic would be very nice to have in the copy job, but I would assume that they are not going to implement that
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
Thanks for sharing. The product needs to be get updated instead of insertion.
You're welcome! What comes to that thing with that update, it is a build in feature since setting up that kind of update logic would be far more complex than this insertion logic. Now I image that this is just using some type of SQL query on the background to get values that have been added/changed after the previous run like this:
SELECT
col1
,col2
FROM source
WHERE col2 > saved_value_for_col2
-> Then this logic will just insert the rows that result from this query and save the largest value for col2 for the next run.
--> That update logic (and also delete) logic would be very nice to have in the copy job, but I would assume that they are not going to implement that