[sqlite] Using date fields in SQLiteExplorer

Here is another question about dates and SQLiteExplorer (v 1.7). I'm storing dates in the native Delphi format, i.e. as floating point numbers ("dates as text" = FALSE). Whenever I try to update a record that contains such a date, SQLiteExplorer displays the message "unexpected count of affected

[sqlite] Two questions about #PRAGMA SYNCRONOUS

Question 1 Is #PRAGMA SYNCRONOUS a global database setting or is it possible to open two handles on the same database and set two different values for #PRAGMA SYNCRONOUS on the two handles ? Question 2 Is it possible to change the value of #PRAGMA SYNCRONOUS on the same handle during the

[sqlite] How to use PRAGMA SYNCRONOUS ??

Here are a couple of questions for the most expert SQLite users. Question 1 Is #PRAGMA SYNCRONOUS a global database setting or is it possible to open two handles on the same database and set two different values for #PRAGMA SYNCRONOUS on the two handles ? Question 2 Is it possible to change the

[sqlite] Optimal page size

I could not find a document explaining how to find the optimal value for the "page size" parameter. Should I set the page size to match the allocation size (cluster size) of the file system ? Should I set it so that each page contains exactly a given number of records (i.e. no record is split

[sqlite] R: [sqlite] Proposed 3.3.0 changes. Was: 5/2==2

Most of the discussion so far was about proposed change number 2, on the contrary I'm concerned about proposed change number 1. Does this mean that a number that can be stored as an integer will be stored as an integer and, thus, I will need to read it back as an integer ? Here is what I mean:

[sqlite] Separate INTEGER and REAL affinity ?

I read in the "changes" page of the SQLite site that version 3.3.x of SQLite features "Separate INTEGER and REAL affinity". What does this exactly mean ? How is SQLite 3.3.x different from 2.8.x with respect to column affinity ? Thank you, bye

[sqlite] R: [sqlite] support for table partitioning?

> The database already knows exactly where to look for each table when all the tables are in the same file. > All it has to do is "lseek()" to the appropriate spot. How does moving tables into separate files help this or make it any faster? > "Table partitioning" is a technique used to improve