[Implemented] New SQLite with 4.51 ?

[USCode]

PB Team,
Will we be getting the latest version of SQLite with PB 4.51?
Thanks!

[USCode]

If PB 4.51 has an updated SQLite library (3.7.0.1 or greater) then my MANY THANKS to the PB development team!

Otherwise, I need to mention that one of my SQLite databases developed a "disk image malformed" error likely because the SQLite administration tool I was using was at SQLite version 3.7.0, but the PureBasic version of the SQLite library was at 3.6.23.1 and there was an incompatibility between the versions.
This problem was addressed by SQLite version 3.7.0.1: http://www.sqlite.org/changes.html

I don't have the 4.51 RC installed, does anyone know what version of the SQLite library 4.51 RC is using?
You can use this code to find out:

Code: Select all

ImportC "sqlite3.lib"
  sqlite3_libversion()
  sqlite3_version.s{20}
EndImport

Debug PeekS(sqlite3_libversion(), #PB_Any, #PB_Ascii)

Debug sqlite3_version 

FYI - The SQLite "disk image malformed" error was fixed using the sqlite3.exe utility that can be downloaded from the SQLite.org website.
These are the commands I used to fix my database:

sqlite3 MyDatabase.db .dump > MyDatabase.sql
sqlite3 MyDatabase2.db <MyDatabase.sql

[srod]

Your code reports 3.6.23.1

[USCode]

Your code reports 3.6.23.1

Thanks srod. I know they already have a ton on their plate but hopefully the PB team can get an updated version of SQLite library (3.7.0.1 or greater) in 4.51 final.

[Fred]

4.51 is in final state so it will be for the next version.

[Zach]

Fred/Freak


Any update on whether SQLite has/will be updated for the next Beta or 4.6x Final?


As an aside:

If I use my own Internal PB (Currently 4.51) commands, and then later update the code for the newest final, assuming the new SQLite is put into it, will the corruption bug crop up in my DB file?

I don't plan on reading/writing across tools built with different versions of PB. I would use 4.51 until the new version came out and then update my code in any needed areas to exclusively use the newer version of PB. At that time I might also write a tool to create a fresh DB and copy the data from the old one into it.

[Fred]

4.60 is in final stage, we won't put an updated SQlite as it requiers some adaptation from us. Probably for the next version then

[Zach]

Thanks for the reply.

Guess we'll have to wait for the next update
I hope you also consider SQLite encryption support for the next update too (here is an open source one - http://sqlcipher.net/ )

[USCode]

4.60 is in final stage, we won't put an updated SQlite as it requiers some adaptation from us. Probably for the next version then

That's what you said last time (4.51)!
Are you aware there's a potential corruption bug with the current version?

[Fred]

There is always hidden bugs in a version, until they got discovered. Does that mean you shouldn't use the software ?

[IceSoft]

There is always hidden bugs in a version, until they got discovered. Does that mean you shouldn't use the software ?

\joke:
Yes of course. We will also use the final PureBasic 4.60 until the bugfix version 4.61 will be released.

[rsts]

4.60 is in final stage, we won't put an updated SQlite as it requiers some adaptation from us. Probably for the next version then

That's what you said last time (4.51)!
Are you aware there's a potential corruption bug with the current version?

You do know you can use any version of the dll you wish using the dll directly? And ts-soft and others have published some excellent prototypes.

cheers

[USCode]

There is always hidden bugs in a version, until they got discovered. Does that mean you shouldn't use the software ?

This current version has the corruption potential but I guess the likelihood someone will still be using 3.7.0 to open an SQLite database created with PB (using 3.6.23.1) is low ...