Eduardo Morras wrote:
> On Sat, 8 Mar 2014 14:09:17 -0500
> Richard Hipp wrote:
>> It isn't really running out of memory
>>
>> The implementation of char() allocates 4 bytes of output buffer for
>> each input character, which is sufficient to hold any valid unicode
>>
On Sat, 8 Mar 2014 14:09:17 -0500
Richard Hipp wrote:
> It isn't really running out of memory
>
> The implementation of char() allocates 4 bytes of output buffer for
> each input character, which is sufficient to hold any valid unicode
> codepoint. But with zero input
It happens on Windows 7 too:
C:\temp>sqlite3
SQLite version 3.8.3.1 2014-02-11 14:52:19
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select char();
Error: out of memory
sqlite> select char(65);
A
sqlite>
___
On Sat, Mar 8, 2014 at 1:25 PM, Zsbán Ambrus wrote:
> In the sqlite3 console, the following very simple statement gives
> "Error: out of memory":
>
> SELECT char();
>
> I think this is a bug. This query should need very little memory, so
> it should not give such an error.
On 03/09/2014 01:25 AM, Zsbán Ambrus wrote:
In the sqlite3 console, the following very simple statement gives
"Error: out of memory":
SELECT char();
I think this is a bug.
It is. Thanks for the report. Now fixed here:
http://www.sqlite.org/src/info/ba39df9d4f
Dan.
This query
On 3/8/14, Simon Slavin wrote:
> SQLite version 3.7.13 2012-07-17 17:46:21
The char function was added in 3.7.16.
> Could you please post your OS and the version of the SQLite shell tool
> you're using ?
I'm using Linux amd64, compiling with gcc 4.8.1. I've got the out
On 8 Mar 2014, at 6:25pm, Zsbán Ambrus wrote:
> In the sqlite3 console, the following very simple statement gives
> "Error: out of memory":
>
> SELECT char();
>
> I think this is a bug.
162:~ simon$ sqlite3 ~/Desktop/test.sqlite
SQLite version 3.7.13 2012-07-17 17:46:21
In the sqlite3 console, the following very simple statement gives
"Error: out of memory":
SELECT char();
I think this is a bug. This query should need very little memory, so
it should not give such an error. I believe it should return a single
row with a single value of an empty string.
I've
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
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
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
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
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
I found the table that I wasn't closing properly, which was locking up my
database. Thanks again, Dr. Hipp, for pointing me in the right direction.
But I just stumbled on another problem. It shouldn't show up in production,
but it wouldn't be good to ignore it, either.
The table I'm
14 matches
Mail list logo