On 24-mei-04, at 14:04, [EMAIL PROTECTED] wrote:
Version 3.0 of SQLite will support unicode in three different representations: UTF-8, UTF-16LE, and UTF-16BE. So the question has come up about what encoding(s) should the COPY command support.
(1) Extend the syntax of the COPY command to allow the user to specify the text representation of the file being imported. (2) Always assume the import is coming from a UTF-8 file.
My vote would be to keep the COPY command for the following reasons:
- Backwards compatibility. I'm sure there are people using this command.
- Every database needs an easy way to get data in and out of the database.
Therefore I prefer to have it built-in, instead of program your own.
If the majority feels it should not be part of the core functionality, I would choose for a compile time option. This alternative keeps everybody happy. But I doubt if the overhead is that significant.
Best,
- Rob Laveaux
-------------------------------------------------------- Pluggers Software Thijssestraat 203 2521 ZG Den Haag The Netherlands
Email: [EMAIL PROTECTED] Website: http://www.pluggers.nl
--------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
