Re: [sqlite] Threading makes SQLite 3x slower??

I was hoping they wouldn't block each other because it's a read lock. I tried making an index on all the columns, but R*tree table + JOIN that I'm using runs about 10x faster. I might have done something wrong, so I'm open to suggestions on a better index, though. I don't think that UPDATEing

Re: [sqlite] Threading makes SQLite 3x slower??

On 4 Aug 2011, at 3:07am, Seth Price wrote: > The full DB has around 17 million rows in it, and for each row I am trying to > count all rows with similar characteristics, divided into different > classifications. I was already able to improve speed 10x by using the R*tree > extension to

[sqlite] Threading makes SQLite 3x slower??

Hey all, I have a small DB bound application that I'm working on. I expect that it will take 10-20 days to run when I'm done with it. So I'm trying to make it multithreaded. But after spending all afternoon getting threading going, it runs on the order of 3x slower per query when I go from one

Re: [sqlite] group_concat and empty strings

sqlite> .null NULL sqlite> select group_concat(''); NULL sqlite> select group_concat(x''); NULL sqlite> I would think it is a bug. At the very least, it is not consistent with the description of the function. It seams to happen only when the only thing being concatenated is a zero length

Re: [sqlite] Fwd: Re: assert() in debug build when running query

On Wed, Aug 3, 2011 at 10:07 AM, Dan Kennedy wrote: > > > Original Message > Subject: Re: assert() in debug build when running query > Date: Wed, 03 Aug 2011 15:00:46 +0200 > From: Jens Miltner > To: General Discussion of SQLite Database

Re: [sqlite] Deep copy of 2 sqlite3*?

On Wed, Aug 3, 2011 at 4:20 AM, Nikki Tan wrote: > Hi sqlite-users! >It's just that I'm writing a copy constructor of my own mini sqlite > wrapper, and I ended up having to do a deep copy of a sqlite3* points to a > SQLite connection. And I'm just wondering is it okay

Re: [sqlite] New columns or tables corruption

Thanks!! You helped me a lot!! Simon Slavin-3 wrote: > > > On 3 Aug 2011, at 1:49pm, LiranR wrote: > >> I want to use sqlite to store information every 3 seconds. I have to save >> a >> lot of information for different time periods. Now, I am worry about a >> power >> fault in the system. I

Re: [sqlite] Deep copy of 2 sqlite3*?

On Wed, Aug 3, 2011 at 12:56 PM, Teg wrote: > I'd suggest either not doing it (prevent the copy constructor from > compiling by declaring it private) or doing it by passing ownership of > the connection around as if it was a socket or file handle. > +1 to that. It is "almost

Re: [sqlite] New columns or tables corruption

On 3 Aug 2011, at 1:49pm, LiranR wrote: > I want to use sqlite to store information every 3 seconds. I have to save a > lot of information for different time periods. Now, I am worry about a power > fault in the system. I know that when i enter data to the DB it makes a > journal so it can roll

[sqlite] Fwd: Re: assert() in debug build when running query

Original Message Subject: Re: assert() in debug build when running query Date: Wed, 03 Aug 2011 15:00:46 +0200 From: Jens Miltner To: General Discussion of SQLite Database Sorry, should have mentioned that this happens with version

[sqlite] New columns or tables corruption

Hi all. I want to use sqlite to store information every 3 seconds. I have to save a lot of information for different time periods. Now, I am worry about a power fault in the system. I know that when i enter data to the DB it makes a journal so it can roll back if the power was shut down in the

Re: [sqlite] Deep copy of 2 sqlite3*?

Hello Nikki, I'd suggest either not doing it (prevent the copy constructor from compiling by declaring it private) or doing it by passing ownership of the connection around as if it was a socket or file handle. That's how I do sockets. If my socket class gets copy constructed to a new class,

[sqlite] group_concat and empty strings

On http://www.sqlite.org/cvstrac/tktview?tn=3806 this bug is fixed. But I still get a NULL with group_concat(distinct x) with the latest windows sqlite shell: SQLite version 3.7.7.1 2011-06-28 17:39:05 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .null NULL

Re: [sqlite] Case Insensitive String comparison

Hi All, I found it myself. For WHERE IN clause, COLLATE NOCASE should be after column name (previously, i tried it by placing it after the expression) eg, SELECT name FROM table WHERE name COLLATE NOCASE IN ('arjabh','ABC') Thanks and Regards, Arjabh On Wed, Aug 3, 2011 at 11:30 AM, arjabh say