While the import works without any problem, there's no way to make sense of the data source. For example, on after import, I may want to post-process the data, filtered by some condition. While this may not be an issue if a single user imports a single csv to a table, if there are more files being imported to the same table, this can lead to a mixup in the data.
It would be very good to add some kind of ID for the imported file, so we know where it came from. The simplest way, IMHO, would be to optionally save the filename in a column. Or, in a more advanced way, provide the option to the developer to add some kind of GUID in a column. This way, it'd be possible to understand where the data came from.
While the import works without any problem, there's no way to make sense of the data source. For example, on after import, I may want to post-process the data, filtered by some condition. While this may not be an issue if a single user imports a single csv to a table, if there are more files being imported to the same table, this can lead to a mixup in the data.
It would be very good to add some kind of ID for the imported file, so we know where it came from. The simplest way, IMHO, would be to optionally save the filename in a column. Or, in a more advanced way, provide the option to the developer to add some kind of GUID in a column. This way, it'd be possible to understand where the data came from.