Message from @Nine
Discord ID: 474713902442217483
yeah you can't do that
I've already got uneven records in my table.
That's the problem.
you might be able to use quotes
Ah. Do you know what the uneven records correspond to?
If all you know is that you have uneven records, it might be something in the commas or the null entries.
It's made uneven the first time a coma appears in the metadata
yup
That should be one row, right?
you need to take source data
It occasionally happens in the artist
Ah wait. so like, the comma is in the title?
usually happens in the Composer
yeah
Occasionally.
so
I'd bitch at your source
Ohhh boy. So there is a regex for that.
because they're dumb
I am the source.
oh
well bitch at yourself
I'm the one that ran intake on all of this
I'm required to mark the composers
.tsv would be better if you can choose the export format.
ok so what did you pull from?
mp3 tags?
reading the mp3 tags on the file?
Yes, the tags on the MP3s
Same as csv but uses tab as the delimiter and can be read just about the same.
yeah tab delimited would be better here
because its very hard progmatically
So here's the thing. it might be able to do some backtrack nonsense to regex it. But you'll need to tell us what you know about each field.
to determine a comma that needs replaced
on any random line
its better not to do it from the beginning
Like, you'll have to be able to tell if the comma is separated somehow from the composer or the delimiter.
honestly
and you mgiht not like this
So you'd be counting characters between commas and guessing what kinds of things go in each field.