You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks again for this great tool. I've got one suggestion to make it even better.
By my side, when I create a csv file, I try to tell apart NULL value and empty string.
Here is an example with comma separator:
• ,, means NULL
• ,"", means empty string
In fact, all my strings are encapsulated by double quotes: ,"My string",
For me, numerical values, booleans and timestamps are not string: ,1234567890,
For my use case, the solution could be:
If input field of csvdiff is encapsulated by double quotes, output field of csvdiff must be encapsulated too (even if output value is empty).
Best regards,
Ben
The text was updated successfully, but these errors were encountered:
In Golang, nulls cannot be stored as a string. It is read as an empty string by the csvreader. Only a pointer can store nils. I will think about a solution for this.
Hello,
Thanks again for this great tool. I've got one suggestion to make it even better.
By my side, when I create a csv file, I try to tell apart NULL value and empty string.
Here is an example with comma separator:
•
,,
means NULL•
,"",
means empty stringIn fact, all my strings are encapsulated by double quotes:
,"My string",
For me, numerical values, booleans and timestamps are not string:
,1234567890,
For my use case, the solution could be:
If input field of csvdiff is encapsulated by double quotes, output field of csvdiff must be encapsulated too (even if output value is empty).
Best regards,
Ben
The text was updated successfully, but these errors were encountered: