Re: [sqlite] Final preparations for the release of System.Data.SQLite v1.0.102.0 have begun...

2016-06-15 Thread R.A. Nagy 
... neither did the Vulcan high command ...  ;-)

On Wed, Jun 15, 2016 at 2:07 PM, R Smith  wrote:

> Bit of an unfair deadline there Joe, Einstein didn't think it plausible.
>
>
>
> On 2016/06/15 7:53 PM, Joe Mistachkin wrote:
>
>> If you have any issues with the current code, please report them via this
>> mailing
>> list (and/or by creating a ticket on "https://system.data.sqlite.org/;)
>> prior to
>> Friday, April 15th.
>>
>> Thanks.
>>
>> --
>> Joe Mistachkin
>>
>> ___
>> sqlite-users mailing list
>> sqlite-users@mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite in Android N

2016-06-15 Thread Simon Slavin 

On 15 Jun 2016, at 8:21pm, Eric Sink  wrote:

> FWIW, I wrote a blog entry about this issue to shine a bit more light on it:
> 
> http://ericsink.com/entries/sqlite_android_n.html

"GitHub says the sqlite-net library has 857 forks"

OMG.  /me hides under bed.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLite in Android N

2016-06-15 Thread Eric Sink 
FWIW, I wrote a blog entry about this issue to shine a bit more light on it:

http://ericsink.com/entries/sqlite_android_n.html

--
E


On Mon, Jun 13, 2016 at 3:51 PM, Richard Hipp  wrote:

> On 6/13/16, Eric Sink  wrote:
> > "Richard (et al), you no doubt have some contact with the Android folks
> at
> > Google.  Do you have any information you can share about these issues?"
> >
> > I don't think I've seen any reply to this question.  It was a yes/no
> > question, so I *could* interpret radio silence as "no".  :-)
>
> I don't have any information on Android N, unfortunately.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [sqlite-dev] Final preparations for the release of System.Data.SQLite v1.0.102.0 have begun...

2016-06-15 Thread Joe Mistachkin 

Eric Sink wrote:
>
> The next time April 15th falls on a Friday is 2022, so I guess we have
plenty
> of time.
>

Actually, it did say Monday, June 20th before I sent it; however, my mail
client
is apparently acting up. 

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Final preparations for the release of System.Data.SQLite v1.0.102.0 have begun...

2016-06-15 Thread R Smith 

Bit of an unfair deadline there Joe, Einstein didn't think it plausible.


On 2016/06/15 7:53 PM, Joe Mistachkin wrote:

If you have any issues with the current code, please report them via this
mailing
list (and/or by creating a ticket on "https://system.data.sqlite.org/;)
prior to
Friday, April 15th.

Thanks.

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Final preparations for the release of System.Data.SQLite v1.0.102.0 have begun...

2016-06-15 Thread Joe Mistachkin 

If you have any issues with the current code, please report them via this
mailing
list (and/or by creating a ticket on "https://system.data.sqlite.org/;)
prior to
Friday, April 15th.

Thanks.

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Latin-1 characters cannot be supported for Unicode

2016-06-15 Thread Hick Gunter 
HEX() function

-Ursprüngliche Nachricht-
Von: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Wang, Wei
Gesendet: Mittwoch, 15. Juni 2016 11:52
An: SQLite mailing list 
Betreff: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

There are some unintelligible text in my database. Is there any methods to see 
their byte sequence?

Best Regards,
Wang Wei


-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Hick Gunter
Sent: Wednesday, June 15, 2016 4:21 PM
To: 'SQLite mailing list'
Subject: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

The answer is very simple: Do not use ANSI/ISO encoding with SQLite. SQLite 
expects Unicode.

-Ursprüngliche Nachricht-
Von: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Wang, Wei
Gesendet: Mittwoch, 15. Juni 2016 04:44
An: SQLite mailing list 
Betreff: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Under the ANSI encoding environment, I created a table named TEST_PRODUÇÃO in 
the database. Then I opened this database with sqlite-tool. I ran the sql 
statement to query all the tables and found the new created table was shown as 
TEST_PRODU??O. Also this table could not be queried out using the table name  
TEST_PRODUÇÃO. It seemed that this issue was caused by encoding mismatch.

Best Regards,
Wang Wei


-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Chris Brody
Sent: Wednesday, June 08, 2016 4:20 PM
To: SQLite mailing list
Subject: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Hi Wei Wang,

Did you populate the database from the sqlite3 CLI tool, your own C program, or 
from another language?

Do you see this when you create a database from scratch, if you use a database 
created by another program, or in both cases?

If you populated the database from the sqlite3 CLI tool, can you post the 
commands you used to populate the database?

If you populated the database from your own C program, can you post a simple 
test program that populates the database?

If you populated the database from another language, can you post a test 
snippet that shows how you populated the database along with a pointer to which 
library you are using?

What kind of system, CPU, and operating system(s) do you see this behavior on?

It should be no problem for sqlite3 to deal with the Latin-1 characters you are 
using if you do it right. The trick is that sqlite3 is designed to deal with 
both UTF-8 and UTF-16 (le or be). SQLite stores which encoding is used in the 
database. The API allows you to use both UTF-8 and UTF-16 encoding, regardless 
of which encoding is actually used to store the data. I think this is 
documented properly in sqlite.org, and I found an excellent writeup (though 5 
years old)
at: http://www.mimec.org/node/297

I also like the Unicode link from Igor.

Chris

On Wed, Jun 8, 2016 at 3:49 AM, Wang, Wei  wrote:
> Thanks for your reply! But I found the Latin-1 encoded characters are
> listed in the Unicode chart. http://unicode.org/charts/PDF/U0080.pdf
>
>
> Best Regards,
> Wang Wei
>
> -Original Message-
> From: sqlite-users-boun...@mailinglists.sqlite.org
> [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of
> Igor Tandetnik
> Sent: Tuesday, June 07, 2016 10:20 PM
> To: sqlite-users@mailinglists.sqlite.org
> Subject: Re: [sqlite] Latin-1 characters cannot be supported for
> Unicode
>
> On 6/7/2016 3:43 AM, Wang, Wei wrote:
>> I met a problem that was maybe caused by the encoding of SQLite. I inserted 
>> a item which including some Latin1 characters like Ç and  Ã  into a table. 
>> Then I opened the database with SQLite Developer. After I setting the 
>> encoding to ANSI, the display and the query result for that table were OK.
>> However after I setting the encoding to Unicode, these Latin1 characters 
>> could not be displayed normally, and could not be queried out. Please see 
>> the attached pictures for the details.
>
> A byte sequence containing Latin-1-encoded characters Ç or à is not in
> fact a valid byte sequence in any Unicode encoding - neither UTF-8 nor
> UTF-16 nor any other. If you want Unicode data in your database, then store 
> Unicode data, and not ANSI, in your database.
> --
> Igor Tandetnik
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
>

Re: [sqlite] Latin-1 characters cannot be supported for Unicode

2016-06-15 Thread Wang, Wei 
There are some unintelligible text in my database. Is there any methods to see 
their byte sequence?

Best Regards,
Wang Wei


-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Hick Gunter
Sent: Wednesday, June 15, 2016 4:21 PM
To: 'SQLite mailing list'
Subject: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

The answer is very simple: Do not use ANSI/ISO encoding with SQLite. SQLite 
expects Unicode.

-Ursprüngliche Nachricht-
Von: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Wang, Wei
Gesendet: Mittwoch, 15. Juni 2016 04:44
An: SQLite mailing list 
Betreff: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Under the ANSI encoding environment, I created a table named TEST_PRODUÇÃO in 
the database. Then I opened this database with sqlite-tool. I ran the sql 
statement to query all the tables and found the new created table was shown as 
TEST_PRODU??O. Also this table could not be queried out using the table name  
TEST_PRODUÇÃO. It seemed that this issue was caused by encoding mismatch.

Best Regards,
Wang Wei


-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Chris Brody
Sent: Wednesday, June 08, 2016 4:20 PM
To: SQLite mailing list
Subject: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Hi Wei Wang,

Did you populate the database from the sqlite3 CLI tool, your own C program, or 
from another language?

Do you see this when you create a database from scratch, if you use a database 
created by another program, or in both cases?

If you populated the database from the sqlite3 CLI tool, can you post the 
commands you used to populate the database?

If you populated the database from your own C program, can you post a simple 
test program that populates the database?

If you populated the database from another language, can you post a test 
snippet that shows how you populated the database along with a pointer to which 
library you are using?

What kind of system, CPU, and operating system(s) do you see this behavior on?

It should be no problem for sqlite3 to deal with the Latin-1 characters you are 
using if you do it right. The trick is that sqlite3 is designed to deal with 
both UTF-8 and UTF-16 (le or be). SQLite stores which encoding is used in the 
database. The API allows you to use both UTF-8 and UTF-16 encoding, regardless 
of which encoding is actually used to store the data. I think this is 
documented properly in sqlite.org, and I found an excellent writeup (though 5 
years old)
at: http://www.mimec.org/node/297

I also like the Unicode link from Igor.

Chris

On Wed, Jun 8, 2016 at 3:49 AM, Wang, Wei  wrote:
> Thanks for your reply! But I found the Latin-1 encoded characters are 
> listed in the Unicode chart. http://unicode.org/charts/PDF/U0080.pdf
>
>
> Best Regards,
> Wang Wei
>
> -Original Message-
> From: sqlite-users-boun...@mailinglists.sqlite.org
> [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of 
> Igor Tandetnik
> Sent: Tuesday, June 07, 2016 10:20 PM
> To: sqlite-users@mailinglists.sqlite.org
> Subject: Re: [sqlite] Latin-1 characters cannot be supported for 
> Unicode
>
> On 6/7/2016 3:43 AM, Wang, Wei wrote:
>> I met a problem that was maybe caused by the encoding of SQLite. I inserted 
>> a item which including some Latin1 characters like Ç and  Ã  into a table. 
>> Then I opened the database with SQLite Developer. After I setting the 
>> encoding to ANSI, the display and the query result for that table were OK.
>> However after I setting the encoding to Unicode, these Latin1 characters 
>> could not be displayed normally, and could not be queried out. Please see 
>> the attached pictures for the details.
>
> A byte sequence containing Latin-1-encoded characters Ç or à is not in 
> fact a valid byte sequence in any Unicode encoding - neither UTF-8 nor
> UTF-16 nor any other. If you want Unicode data in your database, then store 
> Unicode data, and not ANSI, in your database.
> --
> Igor Tandetnik
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Latin-1 characters cannot be supported for Unicode

2016-06-15 Thread Hick Gunter 
The answer is very simple: Do not use ANSI/ISO encoding with SQLite. SQLite 
expects Unicode.

-Ursprüngliche Nachricht-
Von: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Wang, Wei
Gesendet: Mittwoch, 15. Juni 2016 04:44
An: SQLite mailing list 
Betreff: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Under the ANSI encoding environment, I created a table named TEST_PRODUÇÃO in 
the database. Then I opened this database with sqlite-tool. I ran the sql 
statement to query all the tables and found the new created table was shown as 
TEST_PRODU??O. Also this table could not be queried out using the table name  
TEST_PRODUÇÃO. It seemed that this issue was caused by encoding mismatch.

Best Regards,
Wang Wei


-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org 
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Chris Brody
Sent: Wednesday, June 08, 2016 4:20 PM
To: SQLite mailing list
Subject: Re: [sqlite] Latin-1 characters cannot be supported for Unicode

Hi Wei Wang,

Did you populate the database from the sqlite3 CLI tool, your own C program, or 
from another language?

Do you see this when you create a database from scratch, if you use a database 
created by another program, or in both cases?

If you populated the database from the sqlite3 CLI tool, can you post the 
commands you used to populate the database?

If you populated the database from your own C program, can you post a simple 
test program that populates the database?

If you populated the database from another language, can you post a test 
snippet that shows how you populated the database along with a pointer to which 
library you are using?

What kind of system, CPU, and operating system(s) do you see this behavior on?

It should be no problem for sqlite3 to deal with the Latin-1 characters you are 
using if you do it right. The trick is that sqlite3 is designed to deal with 
both UTF-8 and UTF-16 (le or be). SQLite stores which encoding is used in the 
database. The API allows you to use both UTF-8 and UTF-16 encoding, regardless 
of which encoding is actually used to store the data. I think this is 
documented properly in sqlite.org, and I found an excellent writeup (though 5 
years old)
at: http://www.mimec.org/node/297

I also like the Unicode link from Igor.

Chris

On Wed, Jun 8, 2016 at 3:49 AM, Wang, Wei  wrote:
> Thanks for your reply! But I found the Latin-1 encoded characters are
> listed in the Unicode chart. http://unicode.org/charts/PDF/U0080.pdf
>
>
> Best Regards,
> Wang Wei
>
> -Original Message-
> From: sqlite-users-boun...@mailinglists.sqlite.org
> [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of
> Igor Tandetnik
> Sent: Tuesday, June 07, 2016 10:20 PM
> To: sqlite-users@mailinglists.sqlite.org
> Subject: Re: [sqlite] Latin-1 characters cannot be supported for
> Unicode
>
> On 6/7/2016 3:43 AM, Wang, Wei wrote:
>> I met a problem that was maybe caused by the encoding of SQLite. I inserted 
>> a item which including some Latin1 characters like Ç and  Ã  into a table. 
>> Then I opened the database with SQLite Developer. After I setting the 
>> encoding to ANSI, the display and the query result for that table were OK.
>> However after I setting the encoding to Unicode, these Latin1 characters 
>> could not be displayed normally, and could not be queried out. Please see 
>> the attached pictures for the details.
>
> A byte sequence containing Latin-1-encoded characters Ç or à is not in
> fact a valid byte sequence in any Unicode encoding - neither UTF-8 nor
> UTF-16 nor any other. If you want Unicode data in your database, then store 
> Unicode data, and not ANSI, in your database.
> --
> Igor Tandetnik
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


___
 Gunter Hick
Software Engineer
Scientific Games International GmbH
FN 157284 a, HG Wien
Klitschgasse 2-4, A-1130 Vienna, Austria
Tel: +43 1 80100 0
E-Mail: h...@scigames.at

This communication (including any attachments) is intended for the use of the 
intended recipient(s) only and may contain information that is confidential, 
privileged