Hi all,
this is my first reply-to post to this mailing list (using gmane nttp interface) so I hope this post passes moderation ok and is correctly threaded and not duplicated...).

Regarding the inability to use databases created on EBCDIC systems on 'normal' systems, my initial thoughts are that sqlite should at least create databases with the magic number 'SQLite format 3' correctly - ie the magic number should be encoded in the source as a hex literal rather than a string.

Regarding codepage conversions, how does this normally work? As Teg said (or alluded to), should it not be the application's responsibly to do the codepage conversion and pass to the sqlite engine the text in the appropriate Unicode encoding (UTF-8/UTF-16) as required. I'm not sure though, if there is a distinction here between using the bind functions of the API vs supplying literal text in the SQL. ** The documentation on the C API does not say a lot about how encodings are handled for text (bound or in the SQL) **. I would expect in any case, if the application is locale aware it should respect the settings of the respective LC_* environment variables and perform the necessary conversions before calling the sqlite functions??

Regarding the specific case of performing EBCDIC<->ASCII conversions on zOS, this is (IMHO) not the approach to take, since (outside of the unix subsystem of zOS) any EBCDIC codepage can be in use, and as per the above, a locale aware application should take care of this, rather than leaving it to the sqlite engine.

All the above of course would (again IMHO) be moot for blobs, where everything would be stored as is.

On the subject of support for sqlite on zOS, has anyone investigated the possibility on making the command line interface, or the engine itself (via a custom vfs) support the MVS (record orientated) filesystem?

Please share your thoughts,
Thanks in advance,
k

_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to