×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Roger,
Am 04.06.2021 um 05:43 schrieb Roger Harman <roger.harman@xxxxxxxxxxx>:
Originally, I had *DBLQUOTE for string delimiters (the default). Then, we got a record with a data element for 60" (inch) Gizmo. Well, the double quote hosed that up.
My conclusion is, the middleware is faulty with its export function. I admit, I don't have too much experience with CSV-Imports.
Maybe this flaw can be partly blamed to IBM, interpreting a double quote being set not on field boundary (aka, beginning of line, end of line or immediately preceded or followed by the field separating comma) as delimiter instead of leaving it alone.
My opinion is, that ambiguities must be avoided on the exporting side. So, a " as part of field data should be escaped. But it's easy to forget such corner cases in actual code.
https://en.wikipedia.org/wiki/Comma-separated_values says:
[…] without additional information (such as whether RFC 4180 is honored), a file claimed simply to be in "CSV" format is not fully specified.
:wq! PoC
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
