Hi Peter,
reg. 1)
rev. 80 will allow you to open a file with unicode filename.
Unless you specify your own infile handler (mysql_set_local_infile_handler)
the client expects that the character set of the file matches the client
character set of your connection. This is the same behaviour as in My
Could I ask for a reply here - in particular to the 2nd point about SQLite?
What is the advantage of having the SQLite codebase as part of the MariaDB
C-API as compared to getting the SQLite library from the official SQLite
webiste and link in an application?
If there is more to it than just *incl
And also .. the revisions listing at Launchpad (
http://bazaar.launchpad.net/~georghd/mariadb-native-client/1.3/changes/)
stops at revision 32, it seems. If it is not maintained I think it is
better to delete/truncate it. Besides I am also surprised to se the version
listed as "1.3". But maybe I d
This is probably for Georg Richter (and/or @Wlad). I have a few qeustion!
1)
https://bazaar.launchpad.net/~maria-captains/mariadb-native-client/trunk/revision/80
"Fix for CONC-44: LOAD DATA INFILE can't open utf16le encoded filenames"
But we we can stil not specify UTF16LE as the CHARSET, I think
4 matches
Mail list logo
