A less cryptic error message would be useful here though... perhaps you[1] should consider: - Mention that clob stands for "string with unbounded length" - Mention that the reason the data is not a proper clob is an encoding problem - Mention which encoding is expected. - (Maybe) Mention the position in the octet stream at which the decoding failure occurred - (Maybe) Provide the context of decoded characters, e.g. "The quick brown fox ... etc ... lazy d\xDE\xAD\xBE\xEF" - Repeat Stefan's explanation on this wiki page: https://www.monetdb.org/Documentation/Manuals/SQLreference/BuiltinTypes Eyal [1] - Soon I'll need to start writing "we", I suppose, and maybe start owning a few of these issues :-) On 23/07/2015 22:41, Stefan Manegold wrote:
Hi,
internally, MonetDB only handles UTF-8 encoded (textual) data.
Thus, as documented [1], for bulk data load from a file, MonetDB requires the file to use UTF-8 encoding, while for bulk data load via STDIN, MonetDB requires the data to use the same encoding as mclient (see also [2]).
If your data is not in the required encoding, you'd first need to convert it before loading it into MonetDB.
Best, Stefan
[1] https://www.monetdb.org/Documentation/Manuals/SQLreference/CopyInto [2] https://www.monetdb.org/Documentation/mclient-man-page
----- On Jul 23, 2015, at 6:42 PM, Tri Vuong trivektor@gmail.com wrote:
Hi,
I'm using "COPY INTO" to insert some data into MonetDB. The csv that I'm copying from has some weird characters like \367\251\240 in some string fields and it broke the insertion. The error that I got is:
!value from line x field y not inserted, expecting type clob
Does anyone know how to get around this problem? The version I'm using is MonetDB Database Server Toolkit v1.1 (Oct2014-SP4). Thanks.
-- Tri Vuong
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list