It looks like I solved it. I added two new entry points with the _v2 specifications that just invoke the original (v1) code into my own extension code, compiled and Voilá! It works. And the version now says 3.8.0. Of course this means that the new v2 functionality can't be used at this time, but I'm not interested in it anyway, so all fine.


On Mon, Sep 30, 2013 at 1:48 AM, Mark Miesfeld <> wrote:
It looks to me like, when we fooled around with this before, SQLite used sqlite3_key() and rekey.  Now in the latest SQLite code they have changed to use sqlite3_key_v2()

You would need to find an updated codecext.c that has an implementation for the _v2 functions.

Mark Miesfeld

On Sun, Sep 29, 2013 at 4:35 PM, Mark Miesfeld <> wrote:
On Sun, Sep 29, 2013 at 3:32 PM, Staffan Tylen <> wrote:

BUT, now something else happens:
sqlite3.obj : error LNK2019: unresolved external symbol _sqlite3_key_v2 referenced in function _sqlite3Pragma

I don't remember exactly how that encrypted stuff works, but I think that function implementation needs to be in the 'extra' code you bring in.

It should be in codecext.c.  But it is not in the version I have from some time ago.  So, I'm assuming because of the _v2 it is new.  You would need to find the implementation of it.

Mark Miesfeld 

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
Oorexx-users mailing list