On Sat, 22 May 2010, Prakash Reddy Bande wrote:
> Me too, all attempts to unsubscribe have failed.
On Sat, 22 May 2010, pcvetsko...@yahoo.com wrote:
> please unuscribed pcvetko...@yahoo.com
Did you try this:
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Enter the email address
Me too, all attempts to unsubscribe have failed. I have put a filter, but still
my .pst is becoming big.
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] On
Behalf Of Pece Cvetkoski [pcvetko...@yahoo.com]
Sent: Saturday, May 22,
Oops -- you're right...I was paying attention to comments and didn't notice the
16 statement that followed it.
Minor documentation boo-boo I guess...
It appears that the "L" produces UTF-32 in Unix and UTF-16 in Windows.
So the code in sqlite3VdbeMemSetStr only copies the "C" in Unix but does
That was it.
I didn't know that the wchar_t has different bit sizes on Linux and Windows.
Thank you very much.
Jay A. Kreibich-2 wrote:
>
>> I know that the SQL syntax is correct and it is possible to execute that
>> source under windows.
>> I don't understand why it doesn't work with Linux.
If i take a look at the declaration of sqlite3_prepare16_v2() it looks like
this:
SQLITE_API int sqlite3_prepare16_v2(
sqlite3 *db,/* Database handle */
const void *zSql, /* SQL statement, UTF-16 encoded */
There is a UTF-16 encoded string needed.
Black, Michael (IS)
please unuscribed pcvetko...@yahoo.com, you insoult my mail, and i want to
unuscribe for your contacts, thanx
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Sat, May 22, 2010 at 09:23:06AM -0500, Black, Michael (IS) scratched on the
wall:
> I think you're making the mistake of thinking that the entire SQL
> string is UTF-16.
It is. That's the whole point of the "16" interfaces.
> Look at the API for sqlite3_prepare16_v2
> SQLITE_API int
I think you're making the mistake of thinking that the entire SQL string is
UTF-16.
Look at the API for sqlite3_prepare16_v2
SQLITE_API int sqlite3_prepare16_v2(
sqlite3 *db, /* Database handle. */
const void *zSql, /* UTF-8 encoded SQL statement. */
It's your data
On Sat, May 22, 2010 at 05:27:24AM -0700, shion scratched on the wall:
>
> Hello,
>
> I already found a lot of threads about the UTF16 topic, but I couldn't solve
> my problem.
> I have the following source code:
>
> sqlite3_open_v2("test.sqlite", , SQLITE_OPEN_READWRITE |
> SQLITE_OPEN_CREATE,
Hello,
I already found a lot of threads about the UTF16 topic, but I couldn't solve
my problem.
I have the following source code:
sqlite3_open_v2("test.sqlite", , SQLITE_OPEN_READWRITE |
SQLITE_OPEN_CREATE, 0);
sqlite3_exec(Database, "PRAGMA encoding = \"UTF-16\"", 0, 0, 0);
Quoting A.J.Millan:
> Thanks but I'd like to pack the main application and SQLite into a
> single executable, so languages like Python, PHP, etc. aren't good
> solutions.
Take a look at REALbasic (http://www.realsoftware.com/), now called
REALStudio. It has SQLite support built in (and support
11 matches
Mail list logo
