Re: [sqlite] "string or blob too big" issue on a corrupted db

This was a one-time occurrence. No specific way to reproduce the problem is reported. Thanks. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] "string or blob too big" issue on a corrupted db

On 8/2/16, Youngjoon Lee wrote: > Hi, > > Is there any investigation or guess ? > Any answer would be appreciated. I am sorry. I do not know how your database got into its current state. Is the problem reproducible? Or was this a one-time occurrence? -- D. Richard

Re: [sqlite] "string or blob too big" issue on a corrupted db

Hi, Is there any investigation or guess ? Any answer would be appreciated. Thanks. 2016. 7. 29. 오후 12:39에 "Youngjoon Lee" 님이 작성: > ./showdb my-db dbheader > > Pagesize: 4096 > Available pages: 1..745888 > 000: 53 51 4c 69 74 65 20 66 6f 72 6d 61 74 20 33 00 SQLite format

Re: [sqlite] Patch to remove some "unused variable" warnings

Actually, this one part of the patch does not involve #ifdef-ery and so it can be (and has been) applied. On 8/2/16, Andy Gibbs wrote: > > Index: src/date.c > == > --- src/date.c > +++ src/date.c > @@

[sqlite] Vulnerability disclosure - SQLite

Hello, I just finished a security audit to parts of the updated (trunk) code version, and found a probably major vulnerability. I wanted to know what is the preferred way to disclose the findings, as I don't feel comfortable to send it to a large and public mailing list. The report was

Re: [sqlite] Vulnerability disclosure - SQLite

On 8/2/16, Eyal Itkin wrote: > Hello, > > I just finished a security audit to parts of the updated (trunk) code > version, and found a probably major vulnerability. I wanted to know what is > the preferred way to disclose the findings, as I don't feel comfortable to > send

Re: [sqlite] Patch to remove some "unused variable" warnings

On 8/2/16, Andy Gibbs wrote: > On Tuesday 02 Aug 2016 22:07:32 Andy wrote: >> Hi, >> >> I've attached a very small patch that eliminates a few "unused variable" >> warnings that occur when compiled with various OMIT_* options. >> Thanks for the patch, Andy. It is

Re: [sqlite] Patch to remove some "unused variable" warnings

On Tuesday 02 Aug 2016 22:07:32 Andy wrote: > Hi, > > I've attached a very small patch that eliminates a few "unused variable" > warnings that occur when compiled with various OMIT_* options. > > Cheers, > Andy Sorry, this time with inline patch... Index: src/build.c

[sqlite] Patch to remove some "unused variable" warnings

Hi, I've attached a very small patch that eliminates a few "unused variable" warnings that occur when compiled with various OMIT_* options. Cheers, Andy ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Strange SQLite bug(?!)

Thanks! In the meantime I found out that version 3.8.8.3 is still working while 3.9.0.0 fails. Regards, Hartwig > Am 2016-08-02 um 18:47 schrieb Dan Kennedy : > > On 08/02/2016 01:01 PM, skywind mailing lists wrote: >> HI, >> >> it seems to be that I am not allowed to

Re: [sqlite] Branch Apple-OSX

On 8/2/16, skywind mailing lists wrote: > > I have seen that the branch Apple-OSX is still active. Is there any reason > why the contents of this branch are not merged into trunk? Or is the trunk > always merged into Apple-OSX? What is the best branch to use for OS X /

Re: [sqlite] Strange SQLite bug(?!)

On 08/02/2016 01:01 PM, skywind mailing lists wrote: HI, it seems to be that I am not allowed to add zip files to these e-mails. Thanks for reporting this. Should now be fixed here: http://sqlite.org/src/info/e64a4173d2899acf Dan. This is what I am doing to create the database:

[sqlite] Branch Apple-OSX

Hi, I have seen that the branch Apple-OSX is still active. Is there any reason why the contents of this branch are not merged into trunk? Or is the trunk always merged into Apple-OSX? What is the best branch to use for OS X / iOS? Regards, Hartwig

[sqlite] Countdown hold. Was: Testing begins on the SQLite "pi" release

Testing for the SQLite "pi" release is on hold pending the resolution of a design question. Everything appeared to be working well. But there are some design issues that need to be settled before the release, and so we are instituting a hold until they can be fully worked out. On 8/1/16,

Re: [sqlite] Failed to install Microsoft Visual C++ Runtime

Our experience might not apply completely, but we just went through moving to VS2015, but because of all of the vcredist issues with the new version (involving the UCRT), we had to go back to VS2012. Note that installing vcredist: “To install this update, you must have April 2014 update

Re: [sqlite] Strange SQLite bug(?!)

HI, it seems to be that I am not allowed to add zip files to these e-mails. This is what I am doing to create the database: ExecuteStatement(databaseHandle,"CREATE TABLE A(ID INTEGER PRIMARY KEY,AnotherID INTEGER, Notes TEXT);");