« first day (2422 days earlier)      last day (758 days later) » 

Lurch
Lurch
12:00 AM
RELOAD!
 
 
17 hours later…
Duga
Duga
4:34 PM
 
FreeMan
FreeMan
Weird SSIS issue... I've got a package that had been working but now isn't. It looks like the file format changed by adding an additional column. There error I'm getting is
> Data Flow Taks - Load CSV to Temp: Error: The column delimiter for column "ticket_status" was not found.
 
Simon Forsberg
Simon Forsberg
@Duga @MathieuGuindon Guess who's back!
3
(Hint: It's not me)
 
FreeMan
FreeMan
I refreshed the connection manager to read in the new column and it shows this:
note that the column header has quotes around it, as do the values, but none of the other columns have quotes nor do any of the values.
Guess this woulda been a better screen shot showing the lack of quotes on other data
here's the formatting for the connection manager:
This is what the column headers look like in the CSV (as displayed by N++)
and this is the end of a row of data from that file:
> "Open Question - Yes","","","","-1"
What am I missing here?
Oh, maybe after making these changes I failed to deploy the update... :/
@SimonForsberg Welcome back to the boths of ya!
nope, that wasn't it. Just deployed and ran it again and still giving me the same error.
 
HackSlash
HackSlash
5:16 PM
@FreeMan have you verified that the commas are all identical characters? I'm not aware of any stray characters that look like commas but this sort of thing does happen all the time. The error is pretty clear about the delimiter being the problem.
 
FreeMan
FreeMan
well... no... I haven't. What you see above is an exact copy/pasta from the file. I'll ask NPP if it can show me the ASCII!
OK, I see no way to display ASCII in NPP, but I did a search for , (as typed directly on my US-spec keyboard) and it found the comma in the header row and in a couple of test rows.
Hrm... wonder if one of the data rows is short a comma.
no, 110 rows of data. Excel opens the CSV and puts that -1 in the same column for all of them, so I'd presume that it's finding a comma on every row.
 
HackSlash
HackSlash
Are there any unescaped quotes, commas, or line-feeds that could lead to data in the CSV being interpreted as control characters?
 
FreeMan
FreeMan
5:36 PM
Not that I've been able to find. I haven't done an exhaustive search.
any tips on a RegEx to find , that's not in ","? :)
hrm, using Excel to search for , (since it "discards" the "," as it loads the file) I find a lot of them in the free-form user text field. However, all the columns line up properly after that. No data appears to come up short a column or have an extra column appear.
In general, I'd say "no" there aren't any unquoted commas anywhere.
 
M.Doerner
M.Doerner
@Duga Welcome back!
 
HackSlash
HackSlash
That's the low hanging fruit. I would only caution that Excel tends to be "clever" which is to say that it will automatically handle things the way it thinks you want it to. I would expect significant differences between how Excel imports data and anything else, like SSIS
 
FreeMan
FreeMan
5:54 PM
I would too, but I figured it was a good baseline test.
again, suggestions on finding a stray comma in 136k of text?
@FreeMan I too would expect significant differences between Excel and sanity...
 
 
1 hour later…
FreeMan
FreeMan
6:59 PM
hrm, need some Linux, I think. I seem to recall that there were some tools that would give me a count of "," by line. If I find a line that's out of whack with the rest, that'd be the problem.
So far, though, my eyeballing it (I replaced "," with \t in NPP, and turned on viewing the tabs) things seem to be OK for the first 60 lines or so...
 
 
2 hours later…
HackSlash
HackSlash
9:06 PM
Yeah, if you wanna get awkward I'm sure awk could do it. You can run awk from WSL or CygWin, you don't need full Linux install these days
 

« first day (2422 days earlier)      last day (758 days later) »