-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [I changed the order of your questions]
Pierre Cart-Grandjean wrote: > What is recommended to use > instead in the client application? Those are internal undocumented SQLite functions. For example you will see that they are not part of the documented API at http://sqlite.org/c3ref/funclist.html nor do they start with the prefix of all of the api sqlite3_ (note the underscore). The C library does have similar functions (eg stricmp) but because they involve case insensitivity that brings in a whole host of i18n issues. You'll need to decide what to do in your code and what you want to do about the locale, what character set the data is in etc. There is no single answer for everyone. > Why are those functions not extern anymore? They are internal SQLite functions and so should not be used or relied upon by non-SQLite code. Internal functions can be changed or deleted at any point. There is also a case for internal SQLite functions to not "pollute" whatever they are compiled with (eg a containing library/dll/so). For some developers such as myself this is very important: http://www.sqlite.org/cvstrac/tktview?tn=2554 I whine every time some are missed in new releases :-) See the derived tickets list at the bottom of that page. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpX1FkACgkQmOOfHg372QRPJwCgrItHAZOYegKjvBxhtKRtu8U1 qJIAn3brJaY/9gVYp4pgu+g9PPS00c0k =5MwS -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
