Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On Fri, Aug 5, 2016 at 2:03 PM, Dan Kennedy wrote: > On 08/06/2016 03:28 AM, Kevin O'Gorman wrote: > >> On Fri, Aug 5, 2016 at 1:08 PM, David Raymond >> wrote: >> >> .. >> >> Apart from the default location of the files, it reads like your

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On Fri, Aug 5, 2016 at 3:03 PM, Darren Duncan wrote: > On 2016-08-04 7:27 AM, Jim Callahan wrote: > >> Steps >> Agree with Darren Duncan and Dr. Hipp you may want to have at least 3 >> separate steps >> (each step should be a separate transaction): >> >> 1. Simple load

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On 2016-08-04 7:27 AM, Jim Callahan wrote: Steps Agree with Darren Duncan and Dr. Hipp you may want to have at least 3 separate steps (each step should be a separate transaction): 1. Simple load 2. Create additional column 3. Create index Have you pre-defined the table you are loading data

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On 08/06/2016 03:28 AM, Kevin O'Gorman wrote: On Fri, Aug 5, 2016 at 1:08 PM, David Raymond wrote: There's a depreciated pragma, PRAGMA temp_store_directory = 'directory-name'; that apears to still work ok for now at least.

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On Fri, Aug 5, 2016 at 1:08 PM, David Raymond wrote: > There's a depreciated pragma, PRAGMA temp_store_directory = > 'directory-name'; that apears to still work ok for now at least. > http://www.sqlite.org/pragma.html#pragma_temp_store_directory > > I've used it for the

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

There's a depreciated pragma, PRAGMA temp_store_directory = 'directory-name'; that apears to still work ok for now at least. http://www.sqlite.org/pragma.html#pragma_temp_store_directory I've used it for the same reasons you've both mentioned about space, though for me it vacuuming a huge db,

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

On Fri, Aug 5, 2016 at 12:30 PM, Igor Korot wrote: > Hi, Kevin, > > On Fri, Aug 5, 2016 at 3:18 PM, Kevin O'Gorman > wrote: > > Okay, I followed some of the advice y'all gave and got some results. > > > > 1. The original problem was compromised by

[sqlite] Bug in CREATE INDEX

CREATE INDEX has two problems: 1) poor default location of temporary storage. 2) gets wedged on very large indexes. I'm using the sqlite that came with Xubuntu 14.04, I think it's version 3.8.2. I created a table, and used .import to populate it with records, about 1.4 billion of them. The

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

Hi, Kevin, On Fri, Aug 5, 2016 at 3:18 PM, Kevin O'Gorman wrote: > Okay, I followed some of the advice y'all gave and got some results. > > 1. The original problem was compromised by malformed input. However, it > appears that did not cause the wedging of the process.

Re: [sqlite] newbie has waited days for a DB build to complete. what's up with this.

Okay, I followed some of the advice y'all gave and got some results. 1. The original problem was compromised by malformed input. However, it appears that did not cause the wedging of the process. See (3) below. 2. I separated the steps, and started small. Time increased slightly sub-linearly

Re: [sqlite] Partial Index and Query Planner

On 8/5/16, Detlef Golze wrote: > As documented, the query planner only uses the index if the SELECT contains > that exact same condition. > > According to .eqp with 3.12.1 the following statement indeed uses the index: > > SELECT Value1 FROM MyTable WHERE Value1<>0 AND

[sqlite] Partial Index and Query Planner

Hi, suppose I have a partial index like that: CREATE INDEX MyIndex1 ON MyTable ( Value1 ) WHERE Value1<>0; As documented, the query planner only uses the index if the SELECT contains that exact same condition. According to .eqp with 3.12.1 the following statement indeed uses the index:

Re: [sqlite] Network file system

iSCSI is not shared network filesystem file system. iSCSI is a used to mount a local block file system using "SCSI over an IP Network Cable". Without the i the iSCSI protocol is plain SCSI over a SCSI Parallel Cable or sometimes (if you call it SAS) SCSI over a Serial Cable. You can also

Re: [sqlite] Network file system

Il 05/08/2016 09.47, Simon Slavin ha scritto: On 5 Aug 2016, at 7:30am, Michele Pradella wrote: Hi all, I read documentation about using sqlite on a Network file system, so I know is not a good environment because file lock problem. Anyway do you think I can have

Re: [sqlite] Network file system

On 5 Aug 2016, at 7:30am, Michele Pradella wrote: > Hi all, I read documentation about using sqlite on a Network file system, so > I know is not a good environment because file lock problem. Anyway do you > think I can have the same problem if I'm sure that only my

[sqlite] Network file system

Hi all, I read documentation about using sqlite on a Network file system, so I know is not a good environment because file lock problem. Anyway do you think I can have the same problem if I'm sure that only my precess try write or read database? So I have just one process using network DB (for

Re: [sqlite] Get Table names from Database in C++?

Domonic Tom wrote: > Would anyone know how to get the table names from a specific database in C++ > or just using the C API for sqlite? You execute the query "SELECT name FROM sqlite_master WHERE type='table';". > I have tried the below but I get nothing. > > string exec_string = "SELECT name

[sqlite] Get Table names from Database in C++?

Would anyone know how to get the table names from a specific database in C++ or just using the C API for sqlite? I have tried the below but I get nothing. Thought I might be able to move the list of names into a table but it doesn't seem to want to work. Clearly I can't do this using sql..