The csv contains multiple columns (14) , one of which being date / time. If even a figure changes in any column then the row will need to be entered.
If the row is absolutely identical to one already in the table then it should be rejected (ignored), no updating should take place.
Duplication 'should' not occur within the file so there shouldnt be need to dedup that ( however could of necessary :) )
And from what you are saying I should use the database to filter the csv, and such leave just the files NOT in the database. Then upload those files back into the database. If my understanding is correct.
Inserting one at a time is definitely not an option as the csv will contain between 100-500 rows and the database, well 1 csv entered a day, so will grow rapidly
If the row is absolutely identical to one already in the table then it should be rejected (ignored), no updating should take place.
Duplication 'should' not occur within the file so there shouldnt be need to dedup that ( however could of necessary :) )
And from what you are saying I should use the database to filter the csv, and such leave just the files NOT in the database. Then upload those files back into the database. If my understanding is correct.
Inserting one at a time is definitely not an option as the csv will contain between 100-500 rows and the database, well 1 csv entered a day, so will grow rapidly
