[sqlite] about compile configure

2015-12-22 Thread Richard Hipp
On 12/22/15, ??? <2004wqg2008 at 163.com> wrote: >What do you mean of "render the mmap_size mote "? The "PRAGMA mmap_size" command sets the operating-system interface into a mode so that at calls mmap() to read content from disk rather than calling read(). It is often faster to use mmap()

[sqlite] about compile configure

2015-12-22 Thread Richard Hipp
On 12/22/15, ??? <2004wqg2008 at 163.com> wrote: >>> >pragma mmap_size= 51200; >>> >Pragma page_size = 8192; >>> >Vacuum; >>> >Pragma cache_size = N; > The above code has nothing to do with the speed of retrieving records, > especially the beginning retrieve records from database. >

[sqlite] about compile configure

2015-12-22 Thread Keith Medcalf
How long does it take to retrieve one record from the database? How long do you want it to take? > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of ??? > Sent: Tuesday, 22 December, 2015

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Simon Slavin
On 22 Dec 2015, at 1:16pm, Matthias-Christian Ott wrote: > Some software uses the affected versions and it's a good idea they know > that the software is affected. It's a matter of transparency. But it doesn't say when the vulns are fixed so it's not useful to people looking to fix their

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Matthias-Christian Ott
On 2015-12-22 13:48, Richard Hipp wrote: > I do not know where those vulnerability reports originated. They did > not originate from me. For that matter, I was never consulted about > them. None of them represent real vulnerabilities, in my assessment. > All of the problems identified have been

[sqlite] whish list for 2016

2015-12-22 Thread lchis...@paradise.net.nz
Joining the throng, here are my requests: a) Either an ORDER BY clause/equivalent for GROUP BY, or an assurance that the kludge of sorting a sub-query first and then grouping the result does and will continue to work - I need this functionality. b) A separate mailing address for documentation

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Saurav Sarkar
Thanks Clemens for your inputs We are using parametrized queries and don't have any user interface where user can modify anything currently. Its almost a read only application. Our is a file management application But we will come up with some functionality where user will be able to upload

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Saurav Sarkar
Hi All, We use SQlite 3.8.8.3 in our Windows 8.1 universal application. We are also using SQLitePCL as a wrapper to work from c# layer. Our application is free of any kind of SQL injection as we don't have any input fields. We see three vulnerabilities reported recently.

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Simon Slavin
On 22 Dec 2015, at 7:02am, Saurav Sarkar wrote: > But the queries will be always parametrized ones. Exploits 1 and 2 are controlled by things which can't be parameterised. I'm not 100% sure about the format string of a printf, but I can't think of a way to parameterise it. So you would seem

[sqlite] about compile configure

2015-12-22 Thread ηŽ‹εΊ†εˆš
about sqlite3_exec(m_pDB, "PRAGMA synchronous = OFF;", 0,0,0); The testing shows that It can not improve the speed of retrieving records from data base. Thank Simon all the same. At 2015-12-21 18:20:49, "Simon Slavin" wrote: > >On 21 Dec 2015, at 10:07am, ??? <2004wqg2008 at

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Richard Hipp
On 12/22/15, Simon Slavin wrote: > > On 22 Dec 2015, at 7:02am, Saurav Sarkar wrote: > >> But the queries will be always parametrized ones. > > Exploits 1 and 2 are controlled by things which can't be parameterised. > > I'm not 100% sure about the format string of a printf, but I can't think of

[sqlite] SQLite Vulnerabilities reported in NVD

2015-12-22 Thread Clemens Ladisch
Saurav Sarkar: >Our application is free of any kind of SQL injection Famous last words. :) >as we don't have any input fields. So where does your data come from? Does your application have any interface that an attacker could access? How do you create your SQL statements? Are you always using