> > Regarding the sqlite3_exec() should no longer be used for sqlite3 for
> > Unicode application. I am doing the "Begin Transaction" "Commit
> > Transaction"... with the sqlite3_exec(), since this function not
> > supporting Unicode, do you show me how to do a transaction with
> > sqlit3. Wha
[EMAIL PROTECTED] wrote:
D. Richard Hipp wrote:
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
How about the sqlite3_mprintf and sqlite3_vmprintf functions? are
they for the legacy users only?
It is unclear how to add UTF-16 support to those functions.
But they are used intern
D. Richard Hipp wrote:
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
How about the sqlite3_mprintf and sqlite3_vmprintf functions? are they
for the legacy users only?
It is unclear how to add UTF-16 support to those functions.
But they are used internally so they are unlikel
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
> >
> How about the sqlite3_mprintf and sqlite3_vmprintf functions? are they
> for the legacy users only?
>
It is unclear how to add UTF-16 support to those functions.
But they are used internally so they are unlikely to go away.
--
D.
D. Richard Hipp wrote:
On Sun, 2005-02-27 at 22:37 -0400, [EMAIL PROTECTED] wrote:
Hi All,
Anyone have idea when sqlite will support sqlite3_exec16. Since
sqlite3_exec return important error information for the execution error.
Supporting exec16 is urgent for unicode application.
The imp
On Sun, 2005-02-27 at 22:37 -0400, [EMAIL PROTECTED] wrote:
> Hi All,
>
> Anyone have idea when sqlite will support sqlite3_exec16. Since
> sqlite3_exec return important error information for the execution error.
> Supporting exec16 is urgent for unicode application.
>
The implementation of sq
Hi All,
Anyone have idea when sqlite will support sqlite3_exec16. Since
sqlite3_exec return important error information for the execution error.
Supporting exec16 is urgent for unicode application.
Ming
7 matches
Mail list logo
