Re: [sqlite] SQLite policy on compile warnings

Mr. Hipp, On Sat, Jun 25, 2016 at 11:31 PM, Richard Hipp wrote: > On Sun, Jun 26, 2016 at 4:30 AM, Igor Korot wrote: >> >> I am wondering what is the current policy on the compilation >> warning for the SQLite? >> > > In short, the policy of SQLite towards

Re: [sqlite] SQLite policy on compile warnings

Simon, On Sat, Jun 25, 2016 at 11:31 PM, Simon Slavin wrote: > > On 26 Jun 2016, at 3:30am, Igor Korot wrote: > >> ATM I'm using OSX 10.8 with Xcode 5.1.1. compiling everything for C++11 >> and libc++. > > You should not be getting numerous warnings.

Re: [sqlite] Conversion failure

On Sat, Jun 25, 2016 at 11:26 PM, Simon Slavin wrote: > > On 26 Jun 2016, at 2:52am, Igor Korot wrote: > >> Now we need to see the actual German version test result with old and >> new version of the shell tool. > > No need. Given your testing and the

Re: [sqlite] SQLite policy on compile warnings

On 26 Jun 2016, at 3:30am, Igor Korot wrote: > ATM I'm using OSX 10.8 with Xcode 5.1.1. compiling everything for C++11 > and libc++. You should not be getting numerous warnings. One or two, maybe. Make sure that Xcode knows that your .c file is C and not C++. This is a

Re: [sqlite] SQLite policy on compile warnings

On Sun, Jun 26, 2016 at 4:30 AM, Igor Korot wrote: > > I am wondering what is the current policy on the compilation > warning for the SQLite? > In short, the policy of SQLite towards warnings is "Don't Panic!". A "bug" means that the software computes an incorrect answer.

Re: [sqlite] Conversion failure

On 26 Jun 2016, at 2:52am, Igor Korot wrote: > Now we need to see the actual German version test result with old and > new version of the shell tool. No need. Given your testing and the bugfix Keith pointed to I can predict it will work fine for the new version. The

[sqlite] SQLite policy on compile warnings

Hi, ALL, I am wondering what is the current policy on the compilation warning for the SQLite? The reason being - I'm trying to incorporate SQLite into my software. The software will be cross-platform. On both Windows and Linux, I don't see any issues. However, trying to compile on Mac I have a

Re: [sqlite] Conversion failure

> Good news - it looks like the API was fixed as well. I don't have a > crash anymore. > However I have a bad news - the API was fixed in the backward-incompatible > way. > Meaning that running the new DLL against the old database will still > crash. But I guess that is kind of expected. > So

Re: [sqlite] Conversion failure

Simon, On Sat, Jun 25, 2016 at 9:11 PM, Igor Korot wrote: > Simon, > > On Sat, Jun 25, 2016 at 8:32 PM, Simon Slavin wrote: >> >> On 26 Jun 2016, at 1:29am, Igor Korot wrote: >> >>> Now it would be interesting to know what is the

Re: [sqlite] SQLite Logo

The use of the SQLite trademarks is allowed for cases where you want to convey that you are using SQLite are talking about SQLite. But it must be clear to readers that your content is not endorsed by SQLite. An example: there was a product called (something like) "SQLite Database Viewer".

Re: [sqlite] Conversion failure

Simon, On Sat, Jun 25, 2016 at 8:32 PM, Simon Slavin wrote: > > On 26 Jun 2016, at 1:29am, Igor Korot wrote: > >> Now it would be interesting to know what is the result on German >> version of Windows with German >> keyboard. > > Agreed. Anyone from

Re: [sqlite] Conversion failure

On 26 Jun 2016, at 1:29am, Igor Korot wrote: > Now it would be interesting to know what is the result on German > version of Windows with German > keyboard. Agreed. > Also, for my purposes I should be using that version of the SQLite, > right? And everything will just

Re: [sqlite] Conversion failure

Simon, On Sat, Jun 25, 2016 at 8:18 PM, Simon Slavin wrote: > > On 26 Jun 2016, at 1:14am, Igor Korot wrote: > >> That would be 313, correct? > > Yes. The idea is to see if the bug still occurs in the current version. If > it doesn't, it has

Re: [sqlite] Conversion failure

On 26 Jun 2016, at 1:14am, Igor Korot wrote: > That would be 313, correct? Yes. The idea is to see if the bug still occurs in the current version. If it doesn't, it has probably been fixed already. Simon. ___ sqlite-users

Re: [sqlite] Conversion failure

For comparison, here is what I get on my Mac: SQLite version 3.13.0 2016-05-02 15:00:23 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> CREATE TABLE abcß▀(id integer primary key, αΓ string); sqlite>

Re: [sqlite] Conversion failure

Simon, On Sat, Jun 25, 2016 at 8:08 PM, Simon Slavin wrote: > > On 25 Jun 2016, at 5:51am, Igor Korot wrote: > >> This are the results of me trying: >> >> SQLite version 3.9.2 2015-11-02 18:31:45 >> Enter ".help" for usage hints. >> Connected to a

Re: [sqlite] Conversion failure

On 25 Jun 2016, at 5:51am, Igor Korot wrote: > This are the results of me trying: > > SQLite version 3.9.2 2015-11-02 18:31:45 > Enter ".help" for usage hints. > Connected to a transient in-memory database. > Use ".open FILENAME" to reopen on a persistent database. >

Re: [sqlite] Conversion failure

> This are the results of me trying: > > SQLite version 3.9.2 2015-11-02 18:31:45 > Enter ".help" for usage hints. > Connected to a transient in-memory database. > Use ".open FILENAME" to reopen on a persistent database. > sqlite> CREATE TABLE abcß▀(id integer primary key, αΓ string); first >

Re: [sqlite] Conversion failure

Keith, On Sat, Jun 25, 2016 at 10:14 AM, Keith Medcalf wrote: >> > And look in the registry under >> HKLM\CurrentControlSet\Control\NLS\CodePage > >> On my Windows 8.1 machine I don't have HK_LOCAL_MACHINE\CurrentControlSet. > > Ooops. My typo ... > > It is

Re: [sqlite] Conversion failure

> > And look in the registry under > HKLM\CurrentControlSet\Control\NLS\CodePage > On my Windows 8.1 machine I don't have HK_LOCAL_MACHINE\CurrentControlSet. Ooops. My typo ... It is HKLM\SYSTEM\CurrentControlSet\NLS\CodePage > > and report the value for ACP and OEMCP ... > > and also the

Re: [sqlite] Conversion failure

Keith, On Sat, Jun 25, 2016 at 8:43 AM, Keith Medcalf wrote: > > And look in the registry under HKLM\CurrentControlSet\Control\NLS\CodePage On my Windows 8.1 machine I don't have HK_LOCAL_MACHINE\CurrentControlSet. > > and report the value for ACP and OEMCP ... > > and

Re: [sqlite] Conversion failure

Simon, On Sat, Jun 25, 2016 at 4:39 AM, Simon Slavin wrote: > > On 25 Jun 2016, at 5:51am, Igor Korot wrote: > >> So now the question is - what encoding is that value, so that it can >> be successfully converted to wstring? > > Please execute > > PRAGMA

Re: [sqlite] Conversion failure

And look in the registry under HKLM\CurrentControlSet\Control\NLS\CodePage and report the value for ACP and OEMCP ... and also the value returned by the CHCP command at the cmd prompt. > -Original Message- > From: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users- >

Re: [sqlite] Regarding file extension for sqlite command prompt

Use .read to load & execute .sql files. The .open is for databases, not external / textual command files. Here are some introductory videos: https://www.youtube.com/playlist?list=PLItP5KoawLqkPV2jqAVCH79fZGO5k0Uzy On Fri, Jun 24, 2016 at 6:07 AM, Kaja Varunkumar

[sqlite] Regarding file extension for sqlite command prompt

Hello, I am new to SQLite, I have seen the commands for command prompt of SQLite. I have some query files with format .sql. Whenever I try to open the files using command .open and read the files . I am getting an error of file encrypted and not in the database. My question's, are there any

[sqlite] how to use sqlite from classic ASP with no installation...

Hello, I have a classic ASP application running on Windows / IIS to provide that would use an sqlite database. It works fine on my Windows 7 laptop accessing the database using odbc driver. BUT therefore I had to install the odbc driver and needed admin rights to do this install. The person who

Re: [sqlite] Conversion failure

On 25 Jun 2016, at 5:51am, Igor Korot wrote: > So now the question is - what encoding is that value, so that it can > be successfully converted to wstring? Please execute PRAGMA encoding https://www.sqlite.org/pragma.html#pragma_encoding Simon.