This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author msetina
Recipients berker.peksag, erdnaxeli, krypten, msetina, r.david.murray, rhettinger, samwyse, serhiy.storchaka, skip.montanaro, tegdev, yoonghm
Date 2021-09-10.18:28:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1631298491.68.0.969646295753.issue23041@roundup.psfhosted.org>
In-reply-to
Content
The MS Synapse has a CSV support in its COPY command that would benefit from the proposed csv.QUOTE_NOTNULL as it can be used when preparing data for import. As they reference the same RFC the CSV modul should support, both the proposed modifications would extend the RFC functionality with support for NULL/None values in the data.
The csv.QUOTE_STRINGS would enable a smaller file size.
Our case is that we are moving data into Synapse and have to resort to risk prone string replace functionality to provide the MS Synapse COPY a proper support for empty string and NULL
History
Date User Action Args
2021-09-10 18:28:11msetinasetrecipients: + msetina, skip.montanaro, rhettinger, samwyse, r.david.murray, berker.peksag, serhiy.storchaka, krypten, yoonghm, tegdev, erdnaxeli
2021-09-10 18:28:11msetinasetmessageid: <1631298491.68.0.969646295753.issue23041@roundup.psfhosted.org>
2021-09-10 18:28:11msetinalinkissue23041 messages
2021-09-10 18:28:11msetinacreate