SQLite Forum

Version 3.32.1 Compilation Failures
Login

Version 3.32.1 Compilation Failures

(1) By Paul Rotter (protter) on 2020-06-03 13:21:08 [source]

Hello, We've been using SQLite with SEE extensions for many years now and upgrade to the latest version for each release of our product. We've never run into any build problems until we tried to build 3.32.1. The first sign of trouble was missing identifiers: sqlite3_key sqlite3_rekey I thought they may have mistakenly been left out of the sqlite.h file so I moved them into that file and was able to compile. However, other projects in the solution which consume the library failed to find functions: sqlite3PagerSetCodec sqlite3PagerCodec sqlite3PagerState

I've retried a few times with fresh source code, but get the same errors every time. I reviewed the release notes but do not see any indication of a redesign or rearranging of these source files. Can anyone help me to understand what might be wrong and how I can correct it?

Thank you!

Format: Amalgamation

Platform: Windows 10

Tool Chain: Visual Studio 2005

(2) By Stephan Beal (stephan) on 2020-06-03 13:26:34 in reply to 1 [link] [source]

That undocumented/unsupported API was removed. See /forumpost/08481b3fac for details.

(4) By Paul Rotter (protter) on 2020-06-03 13:41:15 in reply to 2 [link] [source]

Thank you, Stephan. Would you be kind enough to provide some further detail?...

Was support for this removed in the 3.32.0/1 release? What made it unsupported if it's been a part of the project for so many years? Was there any announcement for this that I missed?

Forgive my ignorance on this - SQLite has been such a pleasure to work with over the years because it was a black box that was easy to upgrade and just worked.

This is very unsettling as I was not aware of any warnings and this will force us to release our next version with a version of SQLite with three open CVEs...which just means more cover sheets for my TPS reports.

Thank you.

(5) By Stephan Beal (stephan) on 2020-06-03 13:56:33 in reply to 4 [link] [source]

Thank you, Stephan. Would you be kind enough to provide some further detail?...

Forgive my ignorance on this

Likewise, forgive mine: i know nothing about it other than what i incidentally happened to see in the forum post linked to in my initial response and the related post /forumpost/e5a5545a9a.

(3) By ddevienne on 2020-06-03 13:34:19 in reply to 1 [link] [source]

We've been using SQLite with SEE extensions for many years now

DRH decided to break users using an undocumented feature that allows
to implement custom SEE-like code, but I'm sure the official SEE was updated
to work with the latest SQLite. And SEE licensees get a perpetual license.

So visit https://www.sqlite.org/see/doc/release/www/index.wiki and
get an updated version? Assuming you are a licensee of course.

(6) By Paul Rotter (protter) on 2020-06-03 14:06:09 in reply to 3 [link] [source]

Thank you, ddevienne - we do have a license and I will look into that today.

(7) By Paul Rotter (protter) on 2020-06-03 15:33:44 in reply to 6 [link] [source]

Got latest SEE code - issue resolved. Thanks again!

(8) By ddevienne on 2020-06-03 15:44:13 in reply to 7 [link] [source]

Glad I could help, just pointing you in the right direction.