Paul Hatcher
Paul Hatcher
I didn't do the original design but I would guess its about two things 1. Parsing forwards is relatively easy, backwards less so, 2. Keeping all the data on the...
@hugobyrne Same reasons as before, parsing is (potentially) tough, but you could do a couple of things. 1. Do a quick first pass that counts "\r\n" which would give you...
Slightly related point, have you looked at this http://sqlblog.com/blogs/alberto_ferrari/archive/2009/11/30/sqlbulkcopy-performance-analysis.aspx, relatively old, but gives a lot of performance analysis/ideas on SqlBulkCopy
Have a look at the Readme - I've extended the example to show the implementation of AddColumnMapping
@rajeev-ranjan Looking at your code again, it appears you are trying to infer the majority of the headers from the source data but add an explicit column for the filename....
@joeg10 @firthy For issues like this it's much easier to fix if there's a full sample e.g. code, schema and an associated data file. There is some new code which...
@firthy Thanks for that
Thanks for the info - I'll try and have a look at it this weekend
It sounds like a bug - ISTR that SqlBulkCopy was rather strict on the DataTable it will handle e.g. column names and data types have to be aligned Happy to...
You could introduce something that parses it as DateTimeOffset - you have a better chance of it coping if you preserve the timezone information. Happy to accept a pull request