Re: [sqlite] EXT : Unknown module FTS4

Hello, On Mon, Jul 30, 2012 at 6:43 PM, Black, Michael (IS) wrote: > You've got me totally confusedyou say "shared library" and > "dynamically linked" but then say it's embedded in the GUI. > > Which is it? > > Are you on Unix/Linux? > > Can you show us your

Re: [sqlite] Windows I/O (was: Initial read speed greater than subsequent)

On Wed, Aug 1, 2012 at 2:43 PM, Black, Michael (IS) wrote: > You may be interested in this article: > http://www.drdobbs.com/parallel/multithreaded-file-io/220300055?pgno=2 > > Mutli-threaded reading of multiple files (which is basically what you're > talking about by

Re: [sqlite] Documentation bug in result_blob.html

Jesse Weinstein wrote: > > These are not the actual names of the functions. The real names (as > listed at the top of that page) have _error_ in the middle, i.e. > sqlite3_result_error_toobig() and sqlite3_result_error_nomem(). > Thanks. This is now fixed:

Re: [sqlite] Windows I/O (was: Initial read speed greater than subsequent)

On 1 Aug 2012, at 8:25pm, Udi Karni wrote: > - only 2 processes > - only for simple full scans where the block range can be divided in two > - only when there is no ORDER/GROUP BY where sub results from the 2 threads > have to be combined Premature optimization ? SQLite,

Re: [sqlite] Windows I/O (was: Initial read speed greater than subsequent)

You may be interested in this article: http://www.drdobbs.com/parallel/multithreaded-file-io/220300055?pgno=2 Mutli-threaded reading of multiple files (which is basically what you're talking about by splitting a file in half) is only faster if you have multiple disks (in this article that's a

Re: [sqlite] Windows I/O (was: Initial read speed greater than subsequent)

You are right. True Parallel Query can get very complicated. I was hoping for something very limited for starters - for example - - only 2 processes - only for simple full scans where the block range can be divided in two - only when there is no ORDER/GROUP BY where sub results from the 2 threads

Re: [sqlite] SQLITE_STATIC and temporary data

On Wed, Aug 01, 2012 at 04:48:48PM +, Rob Richardson scratched on the wall: > Is "acceptable" good enough? I admit I haven't played with this function > (actually, I never heard of it until today), but from what I read in the > documentation, the case described looked dangerous to me. It's

Re: [sqlite] SQLITE_STATIC and temporary data

Jay A. Kreibich wrote: > On Wed, Aug 01, 2012 at 08:49:19PM +1000, Yose Widjaja scratched on the wall: >> Dear Friends, >> >> So SQLITE_STATIC is meant to be used for data that is static. However, >> would it still be safe when it is used with data that expires after the >> sqlite3_step()

Re: [sqlite] SQLITE_STATIC and temporary data

Is "acceptable" good enough? I admit I haven't played with this function (actually, I never heard of it until today), but from what I read in the documentation, the case described looked dangerous to me. SQLITE_STATIC seemed to me to imply that the contents of the memory used by the sqlite

Re: [sqlite] SQLITE_STATIC and temporary data

On Wed, Aug 01, 2012 at 08:49:19PM +1000, Yose Widjaja scratched on the wall: > Dear Friends, > > So SQLITE_STATIC is meant to be used for data that is static. However, > would it still be safe when it is used with data that expires after the > sqlite3_step() function? > > For example: > >

[sqlite] Documentation bug in result_blob.html

In http://www.sqlite.org/c3ref/result_blob.html it says The sqlite3_result_toobig() interface causes SQLite to throw an error indicating that a string or BLOB is too long to represent. The sqlite3_result_nomem() interface causes SQLite to throw an error indicating that a memory allocation

[sqlite] SQLITE_STATIC and temporary data

Dear Friends, So SQLITE_STATIC is meant to be used for data that is static. However, would it still be safe when it is used with data that expires after the sqlite3_step() function? For example: string hello = "hello world"; sqlite3_bind(statement, 1, hello.c_str(), hello.size(),

Re: [sqlite] Windows I/O (was: Initial read speed greater than subsequent)

On Sat, Jul 14, 2012 at 03:17:07PM +0100, Simon Slavin wrote: > > On 14 Jul 2012, at 3:12pm, Udi Karni wrote: > > > I know > > nothing about writing DB engines - so I don't know whether adding a 2nd > > parallel process adds 10K or 10M to the code base. > > You've reached the

Re: [sqlite] sqlite3_stat problem

Return values are your friends. Use them. Store the error code from every sqlite function call, and if the error code is not SQLITE_OK (NOTE: Check that that is the correct name.), then display what the error code is. In particular, what is the return value of your sqlite3_bind_text()