Re: [sqlite] Thread safety of serialized mode

On Wed, Feb 15, 2017 at 2:07 AM, Jens Alfke wrote: > > Entire programming languages are invited (I'm thinking of > > Java) to make goto and pointers impossible or to make assert() > > impossible (Go) and yet at the same time encourage people to use > > threads. > > [...]. And

Re: [sqlite] Thread safety of serialized mode

Jens Alfke wrote: > With clock speed having stalled, the only way to take advantage of > modern CPUs (and GPUs!) is to go parallel. But "go parallel" does not necessarily imply threads. There are many ways to allow code running on different CPUs(/cores) to communicate with each other (e.g.,

Re: [sqlite] Thread safety of serialized mode

> On Feb 14, 2017, at 5:15 PM, Richard Hipp wrote: > > Nor is there anything wrong with goto, pointers, and assert(), in > principle. And yet they are despised while threads are adored, in > spite of the fact that goto/pointer/assert() errors are orders of > magnitude easier

Re: [sqlite] Storing a INTEGER in a TEXT field

The problem is that you're giving your column a type when you don't want it to have. If the second last line was "message NOT NULL" you'd get exactly what you're asking for. On Wed, Feb 15, 2017 at 1:22 AM, Cecil Westerhof wrote: > I have the following table: > CREATE

Re: [sqlite] OS X/Xcode build error: use of unknown builtin

On 2/14/17, Anthony Chan (antchan2) wrote: > Hello, > > I tried building SQLite 3.17.0 with OSX/Xcode and got the following errors: > We do test extensively on OSX and didn't have any problems. What version of Xcode do you have? -- D. Richard Hipp d...@sqlite.org

[sqlite] OS X/Xcode build error: use of unknown builtin

Hello, I tried building SQLite 3.17.0 with OSX/Xcode and got the following errors: - sqlite3.c:28836:10: error: use of unknown builtin '__builtin_add_overflow' [-Wimplicit-function-declaration] return __builtin_add_overflow(*pA, iB, pA); ^ sqlite3.c:28856:10: error: use of unknown

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On Tue, Feb 14, 2017 at 7:56 PM, Bart Smissaert wrote: > I had to install WinZip though and at the first unzip I got directly to the > files whereas now I had a .tar file first and had to unzip that. > Following on from David Empson's post... the WinZip docs show an

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I expect WinZip defaults to converting text files from Unix to DOS line endings, or you opened and saved the file with something which does the same conversion. I don’t have WinZip handy, but using other tools… My copy of sqlite3.c extracted from sqlite-autoconf-317.tar.gz using Take

Re: [sqlite] Thread safety of serialized mode

On 2/14/17, Darren Duncan wrote: > > There is nothing inherently wrong with threads in principle, Nor is there anything wrong with goto, pointers, and assert(), in principle. And yet they are despised while threads are adored, in spite of the fact that

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

No idea why that is. Could the WinZip alter the file? Another thing is that if I run that sqlite3.c from the MSVS IDE I get the same errors. RBS On Wed, Feb 15, 2017 at 1:11 AM, Cezary H. Noweta wrote: > Hello, > > On 2017-02-15 01:56, Bart Smissaert wrote: > >> Downloaded

Re: [sqlite] Thread safety of serialized mode

On Tue, Feb 14, 2017 at 5:05 PM, Darren Duncan wrote: > On 2017-02-14 4:46 PM, Richard Hipp wrote: > >> This is yet another reason why I say "threads are evil". For >> whatever reason, programmers today think that "goto" and pointers and >> assert() are the causes of

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Hello, On 2017-02-15 01:56, Bart Smissaert wrote: Downloaded again and now it looks more healthy: [...] b0245450e4f27eeefc0da4a871833eb1 sqlite3.c Still not an original one! MD5 of an original ``sqlite3.c'' is 1efd683943e0d2bce1495b3413e2e235. -- best regards Cezary H. Noweta

Re: [sqlite] Thread safety of serialized mode

> On Feb 14, 2017, at 4:46 PM, Richard Hipp wrote: > > This is yet another reason why I say "threads are evil”. I agree, and it’s a pretty widely held opinion these days, going back at least to Edward Lee’s 2006 paper “The Problem With Threads”.[1] Actually the problem

Re: [sqlite] Thread safety of serialized mode

On 2017-02-14 4:46 PM, Richard Hipp wrote: This is yet another reason why I say "threads are evil". For whatever reason, programmers today think that "goto" and pointers and assert() are the causes of all errors, but threads are cool and healthful. Entire programming languages are invited

Re: [sqlite] Storing a INTEGER in a TEXT field

2017-02-15 1:32 GMT+01:00 Simon Slavin : > > On 15 Feb 2017, at 12:22am, Cecil Westerhof > wrote: > > > Is there a way to store an INTEGER in a TEXT field? > > No. But you can do it the other way around. You can store text in an > INTEGER field.

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Downloaded again and now it looks more healthy: C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC>cd C:\SQLite\sqlite-autoc onf-317 C:\SQLite\sqlite-autoconf-317>C:\FCIV\fciv sqlite3.c && nmake /f Makefile.ms c // // File Checksum Integrity Verifier version 2.05. //

Re: [sqlite] Thread safety of serialized mode

> On Feb 14, 2017, at 3:51 PM, Bob Friesenhahn > wrote: > > Due to timing constraints, it performs all read queries in one thread and > creates a temporary POSIX thread for each update query (this is the > developer's reasoning). To me that seems kind of

Re: [sqlite] Thread safety of serialized mode

On 2/14/17, Bob Friesenhahn wrote: > Due to memory constraints > (at least 1MB is consumed per connection!), only one database > connection is used. Any thread may acquire and use this one database > connection at any time. This is yet another reason why I say

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Hello, On 2017-02-15 01:26, Bart Smissaert wrote: OK, that gives this: [...] bd6dfd8b2b566ca64ff9f4c637e533f6 That means, you are not using an original, unmodified sqlite3.c file. Download/unpack an original autoconf package and try once again. -- best regards Cezary H. Noweta

Re: [sqlite] Storing a INTEGER in a TEXT field

On 15 Feb 2017, at 12:22am, Cecil Westerhof wrote: > Is there a way to store an INTEGER in a TEXT field? No. But you can do it the other way around. You can store text in an INTEGER field. Just bind it using sqlite3_bind_textnn() or pass a value delimited by single

Re: [sqlite] Storing a INTEGER in a TEXT field

On 2/14/17, Cecil Westerhof wrote: > Is there a way to store an INTEGER in a TEXT field? No. It will be automatically converted into TEXT. Because that is what PostgreSQL does. -- D. Richard Hipp d...@sqlite.org ___

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

OK, that gives this: C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC>cd C:\SQLite\sqlite-autoc onf-317 C:\SQLite\sqlite-autoconf-317>fciv sqlite3.c && nmake /f Makefile.msc 'fciv' is not recognized as an internal or external command, operable program or batch file.

[sqlite] Storing a INTEGER in a TEXT field

I have the following table: CREATE TABLE messages( messageID INTEGER PRIMARY KEY AUTOINCREMENT, dateTEXT NOT NULL DEFAULT CURRENT_DATE, timeTEXT NOT NULL DEFAULT CURRENT_TIME, typeTEXT NOT NULL, message TEXT NOT NULL ); But for some data the

Re: [sqlite] Thread safety of serialized mode

On Wed, 15 Feb 2017, Simon Slavin wrote: On 14 Feb 2017, at 11:51pm, Bob Friesenhahn wrote: One of our Linux programs (not written by me) is reporting errors of the form "SQLITE_CORRUPT: database disk image is malformed database corruption". Is the database

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Hello, On 2017-02-15 00:53, Bart Smissaert wrote: I tried first with the original source, without altering anything at all. I then had the errors. Could you download and unpack

Re: [sqlite] Thread safety of serialized mode

On 14 Feb 2017, at 11:51pm, Bob Friesenhahn wrote: > One of our Linux programs (not written by me) is reporting errors of the form > "SQLITE_CORRUPT: database disk image is malformed database corruption". Is the database actually corrupt ? Even if your other

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Actually first time I saw these errors the source file and the solution file were on a USB stick and again that worked fine before. RBS On Tue, Feb 14, 2017 at 11:54 PM, Bart Smissaert wrote: > > There's no way to do this on a normal installation that doesn't >

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

> There's no way to do this on a normal installation that doesn't involve modifying the Visual Studio installation directory, Has worked fine before, but will try now with a different directory. RBS On Tue, Feb 14, 2017 at 11:46 PM, Random Coder wrote: > On Tue, Feb

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I tried first with the original source, without altering anything at all. I then had the errors. RBS On Tue, Feb 14, 2017 at 11:38 PM, Cezary H. Noweta wrote: > Hello, > > On 2017-02-14 23:52, Bart Smissaert wrote: > >> I tried both with and without that backslash. >> > >

[sqlite] Thread safety of serialized mode

One of our Linux programs (not written by me) is reporting errors of the form "SQLITE_CORRUPT: database disk image is malformed database corruption". Due to timing constraints, it performs all read queries in one thread and creates a temporary POSIX thread for each update query (this is the

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On Tue, Feb 14, 2017 at 1:23 PM, Bart Smissaert wrote: > C:\Program Files (x86)\Microsoft Visual Studio > 12.0\VC\vcprojects\Win32\SQLite\s > qlite-autoconf-317>nmake /f Makefile.msc What?! You're building from the installation directory? There's no way to do this

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Hello, On 2017-02-14 23:52, Bart Smissaert wrote: I tried both with and without that backslash. ``That backslash''? Did you mean ``Those backslashes''? In the first post you mentioned that the problem concerned ``while'', however in the response to DRH, the first error appeared at ``if''.

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

First time I saw this. Mind you I only use MSVS to compile SQLite. RBS On Tue, Feb 14, 2017 at 10:57 PM, Richard Hipp wrote: > On 2/14/17, Bart Smissaert wrote: > > I just tried with an old 3.11.1 and got different errors: > > When did a "potentially

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 2/14/17, Bart Smissaert wrote: > I just tried with an old 3.11.1 and got different errors: When did a "potentially uninitialized variable" become an error rather than a warning? This is important because MSVC is notoriously bad about overestimating the chances of a

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Yes it looks it is a change in MSVS that is causing this trouble. Not sure now reinstalling is that simple with licensing etc. RBS On Tue, Feb 14, 2017 at 10:49 PM, Simon Slavin wrote: > > On 14 Feb 2017, at 10:47pm, Bart Smissaert > wrote: > >

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I tried both with and without that backslash. No difference. RBS On Tue, Feb 14, 2017 at 10:34 PM, Daniel Anderson wrote: > There is no \ at the end of the code which was pasted. > > did you removed them from the source ? > > the error look related to that problem. > > my

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 14 Feb 2017, at 10:47pm, Bart Smissaert wrote: > I just tried with an old 3.11.1 and got different errors: And if I understand what you wrote earlier, when 3.11.1 came out you were able to compile it without problems. So you seem to have isolated your problem to

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I just tried with an old 3.11.1 and got different errors: Error 1 error C4703: potentially uninitialized local pointer variable 'pDbPage' used c:\program files (x86)\microsoft visual studio 12.0\vc\vcprojects\win32\sqlite\3_11_1\sqlite3.c 57565 1 SQLite Error 2 error C4703: potentially

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

My thinking is that something before line 27461 in sqlite3.c which changed between versions 3.16.2 and 3.17.0 has bumped into a conflict with something defined for your compiler on that computer (e.g. from a Windows header file). If so, you should still be able to compile 3.16.2, which you can

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

There is no \ at the end of the code which was pasted. did you removed them from the source ? the error look related to that problem. my .02 $ 2017-02-14 17:20 GMT-05:00 Simon Slavin : > > On 14 Feb 2017, at 10:15pm, Bart Smissaert > wrote: > >

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 14 Feb 2017, at 10:27pm, Bob Friesenhahn wrote: > On Tue, 14 Feb 2017, Simon Slavin wrote: >> >> There’s always the chance that your copy of VC (or its compiler) got >> corrupted somehow. > > I think that this compiler uses a rolling release model so not

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On Tue, 14 Feb 2017, Simon Slavin wrote: There’s always the chance that your copy of VC (or its compiler) got corrupted somehow. I think that this compiler uses a rolling release model so not everyone is using the same "MSVS 12" compiler. Macros defined by the system headers are the most

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 14 Feb 2017, at 10:15pm, Bart Smissaert wrote: > The strange thing is that nil changed other than moving from version 3.16.2 > to 3.17.0. > There is no serious problem as I can compile on the other PC, but would > like to figure out what is going on here. > Will see

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

The strange thing is that nil changed other than moving from version 3.16.2 to 3.17.0. There is no serious problem as I can compile on the other PC, but would like to figure out what is going on here. Will see if I can look at the pre-processor output. RBS On Tue, Feb 14, 2017 at 10:07 PM,

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

> On 15/02/2017, at 10:23 AM, Bart Smissaert wrote: > > -c sqlite3.c > sqlite3.c > sqlite3.c(16114) : error C2059: syntax error : 'if' > sqlite3.c(16117) : error C2059: syntax error : '}' > sqlite3.c(27461) : error C2143: syntax error : missing ';' before '{' >

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

This is a total shot in the dark... but something with line endings (\r, \n, \r\n, etc.) messing up the #define blah \ Or other things? -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Drago, William @ CSG - NARDA-MITEQ Sent:

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

> -Original Message- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Bart Smissaert > Sent: Tuesday, February 14, 2017 4:24 PM > To: SQLite mailing list > Subject: Re: [sqlite] Problem compiling 3.17.0 in MSVS

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I tried with nmake / Makefile.msc from the VS command prompt but got the same errors: C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC>cd C:\Program Files (x86) \Microsoft Visual Studio 12.0\VC\vcprojects\Win32\SQLite\sqlite-autoconf-317 C:\Program Files (x86)\Microsoft Visual Studio

[sqlite] Can't get Dataset Object to Appear in VB.NET 2015

Hi Folks I'm using System.Data.SQLite successfully for a windows application I'm developing. However, now I need to create and deploy some reports to go with it, and I seem to need a SQLite Dataset / Data Source in the application to point the reports to. I've followed the instructions and

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 2/14/17, Bart Smissaert wrote: > > Should I compile with nmake instead? > Where should I type that? > You can compile however you want, of course. But please know that the Visual Studio point-and-click IDE interface is neither tested nor supported. We developers

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

I am not modifying anything in the source, but I compile with Calling convention: __stdcall (/Gz) as I use the .dll for a VB6 ActiveX dll. I am compiling directly from the VS interface, so via the Build tab and then Rebuild. This always worked fine. I just tried with the smaller file:

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 2/14/17, Bart Smissaert wrote: > The problem seems to be with a #define followed by a opening curly brace, > also for example: > #define WRITE_UTF8(zOut, c) { \ > at line 27227 > > Could it be that VS needs some setting to recognize this construction? > Why does it

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

The problem seems to be with a #define followed by a opening curly brace, also for example: #define WRITE_UTF8(zOut, c) { \ at line 27227 Could it be that VS needs some setting to recognize this construction? RBS On Tue, Feb 14, 2017 at 3:32 PM, Simon Slavin wrote:

Re: [sqlite] Patch for consideration: auto_vacuum slack.

On Mon, Feb 13, 2017 at 9:13 PM, Richard Hipp wrote: > [...] > This makes me want to ask: Is anybody still using auto_vacuum? And > if they are, should they be? I am thinking to change the commonly-used Cordova/PhoneGap sqlite plugin [1] to enable auto-vacuum by default for

Re: [sqlite] 3.17.0 (bug?): ".mode" command ignoring ".separator" when -init used

On Tue, 14 Feb 2017 07:57:17 -0500 Richard Hipp wrote: > It does not ignore it, it overwrites it. The ".mode" command now > always also sets the ".separator" (to the default separator value) for > those modes where the separator is used. This was added to work > around the

Re: [sqlite] Patch for consideration: auto_vacuum slack.

> On Feb 13, 2017, at 12:13 PM, Richard Hipp wrote: > > Does anybody really care anymore that a > database file might have a few dozen pages on its freelist? Or if > they do care, does anybody lack the temp space sufficient to run a > real VACUUM? The issue of vacuuming has

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

On 14 Feb 2017, at 4:42pm, David Raymond wrote: > Correct. Thanks, David. I'd completely missed what this syntax allowed you to do. Simon. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

Correct. -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Tuesday, February 14, 2017 11:08 AM To: SQLite mailing list Subject: Re: [sqlite] bug: fields from external (being updated) table cannot be used in

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

On 14 Feb 2017, at 3:55pm, David Raymond wrote: > It's not. It sets up an alias to a new view of test. In the where clause the > i.whereField is referring to that new view of the whole table, whereas the > test.whereField is referring to the field in the current

Re: [sqlite] sqlite3 hangs on query

On 2/14/17, Igor Tandetnik wrote: > On 2/14/2017 7:33 AM, Jens-Heiner Rechtien wrote: >> please consider the attached dump of a sqlite3 database and the >> following - admittedly nonsensical, don't ask - query over a restored >> version of the database: >> >> *SELECT count(*)

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

It's not. It sets up an alias to a new view of test. In the where clause the i.whereField is referring to that new view of the whole table, whereas the test.whereField is referring to the field in the current record of test that's being updated. So if the table is things, and whereField is the

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

On 14 Feb 2017, at 3:36pm, James K. Lowden wrote: > UPDATE test > SET value = value + 100 * ( > SELECT min(i.value) -- or max, or something > FROM test i > WHEREi.whereField =

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

There is a setting in VS and that says compile as C code. Will start from scratch and make a new VS solution. RBS On Tue, Feb 14, 2017 at 3:32 PM, Simon Slavin wrote: > > On 14 Feb 2017, at 3:06pm, Bart Smissaert > wrote: > > > Yes, didn't

Re: [sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

On Tue, 14 Feb 2017 15:06:16 +0100 Marek Wieckowski wrote: > UPDATE test > SET value = value + 100 *( > SELECT i.value > FROM test i > WHEREi.whereField = test.whereField > ORDER BY

Re: [sqlite] sqlite3 hangs on query

On 2/14/2017 7:33 AM, Jens-Heiner Rechtien wrote: please consider the attached dump of a sqlite3 database and the following - admittedly nonsensical, don't ask - query over a restored version of the database: *SELECT count(*) FROM spacefavorite, album_asset, albums, assetProfileLinks,

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

Yes, didn't expect this was reproducible. All I can think of is that somehow MSVS doesn't recognize this now as C code. Must be one of the settings in VS that has somehow changed. RBS On Tue, Feb 14, 2017 at 2:18 PM, Richard Hipp wrote: > On 2/13/17, Bart Smissaert

Re: [sqlite] Problem compiling 3.17.0 in MSVS 12

On 2/13/17, Bart Smissaert wrote: > Downloaded the latest 3.17.0 (sqlite-autoconf-317.tar.gz > ) and replaced > my old 3.16.2 sqlite3.c file in the VC. Now for some reason I get lots of > errors when

[sqlite] bug: fields from external (being updated) table cannot be used in "order by" clause of a subselect

Hi, Basically: in a subselect in an update statement all fields from the row which is being updated CAN be used in SELECT and WHERE clauses (see the first update below using test.whereField in the WHERE clause), but using them in ORDER BY leads to an error. Example: create table test (

Re: [sqlite] sqlite3 hangs on query

Jens-Heiner Rechtien wrote: > SELECT count(*) > FROM spacefavorite, album_asset, albums, assetProfileLinks, > avatarCacheReferences, > cacheReferences, comment, conflicts, coreInfo, coreMD5, errors, flags, > importSource, missingBinariesOnOz, profileRegistration, quota_exceeded, >

Re: [sqlite] sqlite3 hangs on query

On 14 Feb 2017, at 12:33pm, Jens-Heiner Rechtien wrote: > please consider the attached dump of a sqlite3 database and the following - > admittedly nonsensical, don't ask - query over a restored version of the > database Jens, You can’t send attachments to this list. If

[sqlite] sqlite3 hangs on query

Hi SQLite team, please consider the attached dump of a sqlite3 database and the following - admittedly nonsensical, don't ask - query over a restored version of the database: *SELECT count(*) FROM spacefavorite, album_asset, albums, assetProfileLinks, avatarCacheReferences, cacheReferences,

Re: [sqlite] 3.17.0 (bug?): ".mode" command ignoring ".separator" when -init used

On 2/13/17, Dâniel Fraga wrote: > > The problem is that with version 3.17.0 the .mode line > completely ignore the ".separator ," inside the "-init" file. > It does not ignore it, it overwrites it. The ".mode" command now always also sets the ".separator" (to the

Re: [sqlite] sqlite3_blob_bytes64() ?

> Le 14 févr. 2017 à 12:46, Clemens Ladisch a écrit : > > Olivier Mascia wrote: >> What is the purpose of sqlite3_bind_blob64() and sqlite3_bind_zeroblob64()? > > To allow 64-bit types (but not necessarily 64-bit values). IIRC some > language binding needed this. Seems

Re: [sqlite] sqlite3_blob_bytes64() ?

Olivier Mascia wrote: > What is the purpose of sqlite3_bind_blob64() and sqlite3_bind_zeroblob64()? To allow 64-bit types (but not necessarily 64-bit values). IIRC some language binding needed this. Regards, Clemens ___ sqlite-users mailing list

[sqlite] Documentation change in 3.17.0

Hi, The diff from 3.16.2 -> 3.17.0 contains [[ ** table that is being modified. -** ^The sixth parameter to the preupdate callback is the initial [rowid] of the -** row being changes for SQLITE_UPDATE and SQLITE_DELETE changes and is -** undefined for SQLITE_INSERT changes. -** ^The

[sqlite] Problem compiling 3.17.0 in MSVS 12

Downloaded the latest 3.17.0 (sqlite-autoconf-317.tar.gz) and replaced my old 3.16.2 sqlite3.c file in the VC. Now for some reason I get lots of errors when building a Windows dll. First one is at line 16116 in this code block: #define SQLITE_SKIP_UTF8(zIn) { if( (*(zIn++))>=0xc0 ){