[sqlite] 64bit DLL vs 32bit

> I have found that the Windows 32bit DLL works slower on a 64bit machine > than on a 32bit. I would have thought that the calls from the > applications would have the same response for both machines since the > application is a 32 bit application. Anyone thinks otherwise? Thanks. I presume

[sqlite] SQLite workshop

Cecil, I like the idea but I can't give an outline. It will depend on your audience. Tables, Views, Indexes, Triggers, Joins... One piece of advice I can give you: use an example anyone can understand. I once have a db training and I got lost because the example was about football and the only

[sqlite] Incremental backup/sync facility?

No,you just have to log the bound parameters and a reference to the prepared statement (so the other side will know which statement to prepare). Or just log the statement & the parameters each time. -Original Message- From: sqlite-users-bounces at mailinglists.sqlite.org

[sqlite] 64bit DLL vs 32bit

On 6 May 2016, at 5:36pm, Jose I. Cabrera wrote: > I have found that the Windows 32bit DLL works slower on a 64bit machine than > on a 32bit. I would have thought that the calls from the applications would > have the same response for both machines since the application is a 32 bit >

[sqlite] Incremental backup/sync facility?

Le 14:43 06/05/2016,Simon Slavin ?crit: >On 6 May 2016, at 1:32pm, Stephan Buchert wrote: > >> The largest database file has now grown to about 180 GB. I need to have >> copies of the files at at least two different places. The databases are >> updated regularly as new data from the satellites

[sqlite] 64bit DLL vs 32bit

Greetings! I have found that the Windows 32bit DLL works slower on a 64bit machine than on a 32bit. I would have thought that the calls from the applications would have the same response for both machines since the application is a 32 bit application. Anyone thinks otherwise? Thanks. jos?

[sqlite] Incremental backup/sync facility?

On 6 May 2016, at 3:40pm, Gerry Snyder wrote: > One feature of SQLite -- the whole database in one file -- is normally an > advantage but becomes less so when the file is huge. Believe me. It's still a huge advantage. Have you ever tried to copy a MySQL database off a non-working server by

[sqlite] The Session Extension (future SQLite extension)

On 6 May 2016, at 1:51pm, Richard Hipp wrote: > I bungled the copy/paste of that URL. Should be > https://www.sqlite.org/draft/sessionintro.html That's very interesting. I note that says "This function does not change the

[sqlite] Incremental backup/sync facility?

We are using Sqlite for data from satellite Earth observations. It works very well. Thanks to everybody contributing to Sqlite, uppermost Dr. Hipp. The largest database file has now grown to about 180 GB. I need to have copies of the files at at least two different places. The databases are

[sqlite] Incremental backup/sync facility?

On 5/6/16, Hick Gunter wrote: > No,you just have to log the bound parameters and a reference to the prepared > statement (so the other side will know which statement to prepare). > Or just log the statement & the parameters each time. The sqlite3_trace() interface fills in the values for the

[sqlite] Is it faster with descending index

I prepared a test application on Windows. Used sqlite 3.12.2 32bit DLL. - Just one table in a database. - Database1, Table created with below SQL and second database I included WITHOUT ROWID at the end when creating the test table. - Application filled in 500.000 random value generated records

[sqlite] Incremental backup/sync facility?

On 6 May 2016, at 1:32pm, Stephan Buchert wrote: > The largest database file has now grown to about 180 GB. I need to have > copies of the files at at least two different places. The databases are > updated regularly as new data from the satellites become available. > > Having the copies of

[sqlite] Incremental backup/sync facility?

As an aside, this is how Apple syncs Core Data to iCloud (and then to multiple iOS devices) if the backing store uses SQLite (the default). When a small amount of data changes (which is common), the changes get send out, not the entire (mostly unchanged and potential huge) database. Jeff >

[sqlite] Incremental backup/sync facility?

May I suggest using a statement log of the "primary" database to update the secondary sites? If you have a sequence counter (separate or embedded) then the state of the database could be recovered from a backup (sequence counter x) plus the log files for all statements from x+1 to "current".

[sqlite] Fastest way to backup/copy database?

On 4 May 2016 at 20:39, Rob Willett wrote: > Clemens, > > We have 8GB of memory which is the most our VPS provider allows. We?d like > 32GB but its not an option for us. Our desktops have more than that, but > the VPS provider is reasonably priced :) > > We hadn?t considered the WAL mode, my

[sqlite] Incremental backup/sync facility?

Doesn't this eliminate the use of prepared statements? On 5/6/2016 11:10 AM, Jeffrey Mattox wrote: > As an aside, this is how Apple syncs Core Data to iCloud (and then to > multiple iOS devices) if the backing store uses SQLite (the default). When a > small amount of data changes (which is

[sqlite] Incremental backup/sync facility?

Gerry; I trashed the email I was going to send. You had the same line of thought as me in regards to chopping the file on a per-day basis, but, what made me trash it was any auto-numbered PKs that would be a hassle in new files, unless that information was put into the new DB upon creation. I

[sqlite] Incremental backup/sync facility?

ure Size: 181 bytes Desc: OpenPGP digital signature URL: <http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/attachments/20160506/54cc3faf/attachment.pgp>

[sqlite] Incremental backup/sync facility?

On 5/6/16, Richard Hipp wrote: > On 5/6/16, Simon Slavin wrote: >> >> Believe it or not, the fastest way to synchronise the databases is not to >> synchronise the databases. Instead you keep a log of the instructions >> used >> to modify the database. > > Or, this might be an even better

[sqlite] Incremental backup/sync facility?

On 5/6/16, Simon Slavin wrote: > > Believe it or not, the fastest way to synchronise the databases is not to > synchronise the databases. Instead you keep a log of the instructions used > to modify the database. Or, this might be an even better solution. Note that the sqlite3_trace() function

[sqlite] Incremental backup/sync facility?

On 5/6/16, Stephan Buchert wrote: > > A kind of hack-ish solution might be to update the primary database > files in WAL mode, copy only the WAL file to the secondary place, > and force there WAL checkpoint. Would this work? > This sounds like the most promising solution to me. We'll think on

[sqlite] Incremental backup/sync facility?

On 5/6/2016 5:32 AM, Stephan Buchert wrote: > We are using Sqlite for data from satellite Earth observations. It > works very well. Thanks to everybody contributing to Sqlite, uppermost > Dr. Hipp. > > The largest database file has now grown to about 180 GB. One feature of SQLite -- the whole

[sqlite] strftime accepts an illegal time string

> >For instance, do you care if someone enters a time which is skipped by the >clocks going forward ? If at 1am your clocks skip straight to 2am, do you >care if someone enters a time of 1:30am on that >day ? > > >Simon. > Our local time skips from 2am to 3am and from 3am back to 2am for DST.

[sqlite] .DUMP output compatibility

Windows! -Original Message- From: Richard Hipp Sent: Friday, May 06, 2016 1:55 AM To: SQLite mailing list Subject: Re: [sqlite] .DUMP output compatibility On 5/5/16, Tony Papadimitriou wrote: > Is it possible for .DUMP to produce table/field names quoted with ` > (backquote) instead of

[sqlite] Is it faster with descending index

Hi, I am using SQLite version 3.9.2 on WinCE devices. I have below table in one of my databases. Table sometimes holds 1.5 to 3 million records in it. That database is reached for read-only purposes and created from scratch in a PC if its contents needs to be updated. All database files,

[sqlite] Version of the database

The file header contains the SQLite version that most recently modified the schema. You can see this using the cli, but not a pragma. If you are willing to dig a bit, you can retrieve it by reading the first 100 bytes or so from the file and examining the 4 bytes at offset 96. It's a

[sqlite] .DUMP output compatibility

Is it possible for .DUMP to produce table/field names quoted with ` (backquote) instead of ? (double quote) for compatibility with MySQL? Or is this already adjustable by some setting I missed? Thank you.