Re: [sqlite] In what case will the online backup api hang for acquiring the Btree lock of the destination on-disk file?

Thanks for everybody’s help. Today I did more experiment and finally narrowed down the cause (but not the root cause) of the problem. Under the following situation the in-memory source database and the NFS disk destination database will meet deadlock across 2 threads: * Thread 1 (T1)

Re: [sqlite] Database corruption question

On 20 Jul 2016 at 20:29, Richard Hipp wrote: > On 7/19/16, Doug Nebeker wrote: >> there is only one process using the database file (though multiple >> threads, but they each have their own database handle). > > That threading mode

Re: [sqlite] SQL to SQLite

If you are into Java, then I have a source code generator that should do the trick: https://sourceforge.net/projects/sqlmate/?source=directory All one need do is to use the main.java included in the archive to generate the DAO, then create two connection strings - one for each database file.

Re: [sqlite] SQL to SQLite

Thanks R.A.Nagy. Would you be able to provide a quick example of what you mean? What I ended up doing was iterating through the rows and columns of the SQL database and creating a string that would later be used as an SQLite Insert command. Seemed like that was the long way around. If there's

Re: [sqlite] Database corruption question

On 7/19/16, Doug Nebeker wrote: > there is only one process using the database file (though multiple > threads, but they each have their own database handle). That threading mode (https://www.sqlite.org/threadsafe.html) are you using? Are you sure that you are using the

Re: [sqlite] SQL to SQLite

> Message: 2 > Date: Tue, 19 Jul 2016 15:01:55 -0700 > From: > To: > Subject: [sqlite] SQL to SQLite > Message-ID: <004d01d1e209$2a356360$7ea02a20$@spotlightmusic.com> > Content-Type: text/plain; charset="us-ascii" > > What's

Re: [sqlite] SQL to SQLite

There are several ways to work with other databases. From the SQLite, we can always attach another file so as to work with > 1 database file at a time. From a programmatic point of view, one simply uses yet another database connection to do the same thing. On Tue, Jul 19, 2016 at 7:21 PM,

Re: [sqlite] SQL to SQLite

On 20 Jul 2016, at 12:21am, Robby Helperin wrote: > Any SQLite string is going to refer to just one database, so you can't write > an INSERT command that will take from one database and write to another, or > can you? How would this normally done? See the ATTACH

Re: [sqlite] Database corruption question

On 19 Jul 2016, at 5:43pm, Doug Nebeker wrote: > Would it be possible for a file scanning process (anti-virus, backup, etc) to > grab hold of a database file at just the right moment, momentarily blocking a > write or delete, and causing corruption? It might prevent the

Re: [sqlite] get field precision

On 7/20/2016 6:40 AM, Leonardo Massei wrote: I've a simple question: I need to get the precision (or scale) of a table's field SQLite doesn't have a concept of field precision or scale, so there's nothing to get. See also: http://www.sqlite.org/datatype3.html -- Igor Tandetnik

[sqlite] get field precision

Hello, I've a simple question: I need to get the precision (or scale) of a table's field; there is a sqlite core function ? Is it possible make an SQL command to get the precision ? Best Regards Leonard LEGAL DISCLAIMER: The contents of this email and any transmitted files are confidential

[sqlite] Typographical error in sqlite.org/howtocorrupt.html

I believe that there is a typographical error on the following page: https://www.sqlite.org/howtocorrupt.html *7.4 Database pages leak from the free page list* When content is deleted from an SQLite database, pages that are no longer used are added to a free list and are reused

Re: [sqlite] SQL to SQLite

Thanks for your response. Programming language is definitely the way I want to go, and in fact I programmed a workaround, but I assume I took the long way around and that there's a more standard way to do it. Any SQLite string is going to refer to just one database, so you can't write an INSERT

[sqlite] Database corruption question

Been using SQLite for a long time and a huge fan. We occasionally see database corruption on a local NTFS Windows drive and I've been trying to figure it out. I finally have some logs from the SQLITE_CONFIG_LOG callback that may be of help: (11) database corruption at line 78267 of

Re: [sqlite] In what case will the online backup api hang for acquiring the Btree lock of the destination on-disk file?

On 20 Jul 2016, at 9:03am, Yihong Zhan wrote: > * std::string m_tmpFileName = > "file:/NFS/some_dir/database?mode=memory&=shared”; > * int rv = sqlite3_open_v2(m_tmpFileName.c_str(), _sqlObj, > SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE |

Re: [sqlite] In what case will the online backup api hang for acquiring the Btree lock of the destination on-disk file?

Thanks Quan Yhong. Today I did more experiment and finally narrowed down the cause (but not the root cause) of the problem. Under the following situation the in-memory source database and the NFS disk destination database will meet deadlock across 2 threads: * Thread 1 (T1) creates an

Re: [sqlite] SQL to SQLite

Converting from one SQLite database to another may also be accomplished by using the ".mode insert " output format of the SQLite shell and then SELECTING the rows according to the full target schema. This creates SQL of the form "insert into values (); NOTE: No field list Or you can SELECT