Closed wibeasley closed 7 years ago
Using Quote=FALSE
fix the problem?
That option worked for my specific scenario (which prompted PR #17), but I think always including the quotes is an overall undesirable behavior because
WHERE FindingCategory='Bad'
than WHERE FindingCategory='"Bad"'
.I don't understand the details of the underlying chain using bcp and clCallStatic
. I was hoping those developers had encountered this problem before, and had some option like "IgnoreQuotesDuringUpload".
Thanks @agstudy for all your work on this package. It saves us so much time (over RODBC) with our warehouse-ish projects.
Thank you. Since the end of this year , I will come back to this package to work on it actively and use it as a component from our consulting services. So I will be happy to hear from you and others how do you use this package and what features do you want to include.
Great. I just sent you an invitation on LinkedIn. Contact me when it's best for you, and I'm happy to help.
Is there a way to have the bulk copy mechanism interpret the quotes surrounding character fields, and not upload them to the database. (For my current situation, I could just unquote the temp csv, but I'm hoping there's a more general solution in case the quotes are necessary to handle commas inside the actual values.)
In other words, instead of the default bulk copy resulting in something like this
it would look like this:
I see that
clrCallStatic("rsqlserver.net.misc","SqlBulkCopy",con.string ,value,name)
is called underneath, and you've mentioned the bcp utility in other posts, but I didn't understand how they fit together. Is this a simple configuration change?