putting logic into import of csv files

[marathonsteve]

Describe the new feature

I have imported a csv file and it took fine, but one record has a comma in the record itself. I used HEXEDIT to examine the CSV file and there is no comma after the data value. There are commas in the file as expected to separate the data fields, but nothing but the ODOA values for line feed and carriage control. Not sure if this is an actual bug or some crappy data in the imported file, but I am requesting that the import feature has more validation logic.

Additional info

Please answer these questions before submitting your feature request.

Is your feature request related to an issue? Please include the issue number. No.

Does this feature exist in another product or project? Please provide a link. unknown

Do you have a screenshot? Please add screenshots to help explain your idea.

[chrisjlocke]

If it's one record, it's unlikely to be the code - there would be more errors.
You haven't stated what version of DB4S you're using. This is one area of the program that has received a lot of updates over the years.
Have you split up the data to isolate the issue? Cut the CSV in half, and import A, then import B. Does the error still occur. How about if you just import B? If you split that in half, does it still error?
Is it private data? If you email it to me I can try and import it and see if I can replicate it - if it can be replicated then it can be corrected - with just a vague "add more logic" it's hard to know where the problem lies.

[MKleusberg]

@marathonsteve Can you give us the problematic line of the CSV file? You can also replace some of the data in it as long as it still produces the same results in the import. But without any idea how the original data looks like it's hard to improve our validation logic 😄