Re: [sqlite] Out of memory error

Hi Simon, Thanks for the reply. On 10/9/2013 1:37 AM, Simon Slavin wrote: I do not think this will solve your problem in one go, but execute the SQL command ANALYZE then try it again. If it doesn't help, please post the new query plan. The query plan hasn't changed: 0|0|0|SCAN TABLE

Re: [sqlite] Query preperation time does not scale linearly with growth of no. of tables

Op 9 sep 2013, om 10:06 heeft Harmen de Jong - CoachR Group B.V. het volgende geschreven: Our table and column names are not too long either as E.Pasma suggests. Ha, I did not mean the length of the names but the length of the hash table (NL: klutstabel), That is the number of buckets

Re: [sqlite] Out of memory error

On 9 Sep 2013, at 4:35pm, Mohit Sindhwani wrote: > I just added indexes as best I saw: > * an index on TI(itemid) -- this was already there > * an index on TI(itemid, day) -- I just added this > * an index on WD(day, wday) -- I just added this > * an index on WD(wday) -- I just

Re: [sqlite] Out of memory error

Hi Richard On 9/9/2013 11:10 PM, Richard Hipp wrote: SQLite does not normally *require* a lot of memory. (But it generally runs faster the more memory you give it, so the default configuration is to use as much as it wants.) That is what I have always observed. I'm guessing you have set

Re: [sqlite] Query preperation time does not scale linearl with growth of no. of tables

On Fri, 6 Sep 2013 17:29:25 Harmen de Jong - CoachR Group B.V. wrote > [Explaining why there can be 10,000 tables referencing one table] ... users > can create highly customized research forms with varying number of columns, > varying field types and a lot of specific restrictions, which we

[sqlite] Out of memory error

Hi Guys, I have hit a new problem and would like some advice if there's a way around it. Error: near line 2: out of memory Basically, I have a table with 291 columns, 1.5 million rows. 288 columns have numeric values, additionally there is an itenid and day. I want to use SQL to basically

Re: [sqlite] Out of memory error

On Mon, Sep 9, 2013 at 11:01 AM, Mohit Sindhwani wrote: > Hi Guys, > > I have hit a new problem and would like some advice if there's a way > around it. > > Error: near line 2: out of memory > > Basically, I have a table with 291 columns, 1.5 million rows. 288 columns > have

Re: [sqlite] SQLite Linq not being loaded

I am not familiar with the Windows System.Data.SQLite environment. The maintainer (Joe Mistachkin) is pretty good about catching up to the users list when he has time. Have you tried what's mentioned at the bottom of this page?

Re: [sqlite] SQLite Linq not being loaded

Thanks, but that just confirms what I mentioned which is that SCOPE_IDENTITY is not valid in SQLite. The issue here is that the generation of SQL statements from Linq statements is not being done by System.Data.SQLite.Linq which should be generating the correct syntax. There are other examples of

[sqlite] SQLite 3.8.0 percentile test failure

Hello, I have trouble building the sqlite for i686 architecture. One of the percentile tests (percentile-2.1.50) fails, because it expects result of exactly 274.5 and got 274.50004681, which is very near, but not exact. I've built previous versions without problem, so I guess

Re: [sqlite] SQLite Linq not being loaded

On Sun, Sep 8, 2013 at 2:36 AM, Steve Palmer wrote: > Hi! > > Has anybody successfully used System.Data.SQLite.Linq in their project and > can perhaps help me with this? > > Even after including this DLL in my project reference, it is apparent that > Linq is calling the wrong

Re: [sqlite] SQLite Linq not being loaded

I've not had any response but it seems that System.Data.SQLite.Linq.dll doesn't work with DataContext at all. I'm not sure why it is supplied. I've found no examples of anything that uses this so it doesn't seem worth shipping this. I've found SQLite.Net which is a different C# sqlite wrapper

Re: [sqlite] Query preperation time does not scale linearly with growth of no. of tables

On 7 sep. 2013, at 04:45, "David de Regt" wrote: > Mayhaps the CROSS JOIN trick is your friend in this case, if you can be > pretty sure of the correct direction of the join order. :) In the examples I gave it was actually about a simple delete query from one table without