Hi
Thanks Gerd and Dan and Ryan.
I received answers that helped me understand and solve my problem by
redirecting temp data to a directory rather than in-memory.
I tried Dan's proposal to SETENV TMPDIR and afterwards I could successfully
create index.
I will try Gerd's pragma proposal as well
Hey guys,
I'm getting signal 6 during sqlite_step in WAL mode. Working on Ubuntu
12.04, sqlite3 3.7.9.
One process is the writing continuously, while other process reads from
the DB in a multi threaded access. I made sure that sqlite is configured to
serialised mode.
Here is the backtrace:
#0 0x
IF ResultCode == A_OK YipeeKiAiii else OhShitItDidntWork;
Seems pretty straightforward to me. You handle the result codes you know what
to do with, and everything that remains means your program should explode
immediately and very very loudly dumping ALL relevant information (ie, error
code,
According to the documentation for the xCommit virtual table method "A call to
this method always follows a prior call to xBegin and xSync." However, this
does not seem to be the case when actually creating a virtual table. The
post-create xCommit call is made without any prior xBegin call. S
Hey guys,
How does one accomplish this in the case where I iterate over a long result set
with the first reader open, then open a new reader against a prepared statement
and pass in a value derived from the first reader.
Thanks,
jlc
___
sqlite-users mail
On 30 Jun 2014, at 7:47pm, Eric Rubin-Smith wrote:
> I am a big fan generally of the clarity of the sqlite docs. But this page
> could use another section detailing all the possible result codes' specific
> semantics under sqlite3_step(), and in particular what the client should do
> in those c
I've been using the sqlite Tcl API for about 3 million years, with much
delight. I'm venturing now into the C API -- hoping to put sqlite into a
large monolithic "always on" C++ daemon. I would like to use the API in a
way perfectly in line with how the authors intended.
But it's sort of hard to
Do you possibly have redirected temporary storage to memory, either by
compile switch or #pragma temp_store? If so, try explicitly setting
#pragma temp_store=1, this will force temporary data to be stored on disk.
Gerd.
Hadashi, Rinat schrieb am 30.06.2014 10:30:
I work with a very big table,
Hello,
Are you sure?
http://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html#setSavepoint()
Regards.
On Sun, Jun 29, 2014 at 12:15 PM, hala wrote:
> JDBC does not support savepoints from SQLite
>
> is there any replacement for savepoints?
>
> if not what to use for bulk inserts to ensur
On Mon, Jun 30, 2014 at 12:14 PM, Nick Eubank wrote:
> Sorry, I wasn't clear: I have 64 bit R and Windows, but since there are no
> 64 bit binaries for SQLite I started with 32 bit SQLite.
>
> So now I'm wondering if I could fix this memory problem by installing the
> 64-bit version of SQLite.
>
A 64-bit Windows DLL is now available at http://www.sqlite.org/download.html
On Mon, Jun 30, 2014 at 12:26 PM, Richard Hipp wrote:
>
>
>
> On Mon, Jun 30, 2014 at 12:14 PM, Nick Eubank
> wrote:
>
>> Sorry, I wasn't clear: I have 64 bit R and Windows, but since there are no
>> 64 bit binaries f
Richard, you are my hero. :)
On Mon, Jun 30, 2014 at 9:31 AM, Richard Hipp wrote:
> A 64-bit Windows DLL is now available at
> http://www.sqlite.org/download.html
>
>
> On Mon, Jun 30, 2014 at 12:26 PM, Richard Hipp wrote:
>
> >
> >
> >
> > On Mon, Jun 30, 2014 at 12:14 PM, Nick Eubank
> > wr
Simon Slavin wrote on Monday, June 30, 2014 12:21 PM
>
> SQLite isn't a thing, it's an API. There's no SQLite server. There's
> no particular installation of SQLite on a computer that Windows expects
> to be in a particular place. You can have many copies of many
> different versions of SQLite
On 30 Jun 2014, at 5:14pm, Nick Eubank wrote:
> So now I'm wondering if I could fix this memory problem by installing the
> 64-bit version of SQLite.
SQLite isn't a thing, it's an API. There's no SQLite server. There's no
particular installation of SQLite on a computer that Windows expects t
Sorry, I wasn't clear: I have 64 bit R and Windows, but since there are no
64 bit binaries for SQLite I started with 32 bit SQLite.
So now I'm wondering if I could fix this memory problem by installing the
64-bit version of SQLite.
(I know that this wouldn't fix the problem in postgres, for examp
On 30 Jun 2014, at 4:58pm, Nick Eubank wrote:
> Thanks Cory -- is this fixed in 64 bit versions of SQLite? I know postgres
> never changed memory address variable storage in the 64 bit so the problem
> persists.
You are misunderstanding the problem. There is no bug to be fixed. It is in
the
Thanks Cory -- is this fixed in 64 bit versions of SQLite? I know postgres
never changed memory address variable storage in the 64 bit so the problem
persists.
Also: any advice on getting a 64bit installation for someone who doesn't
really know how to compile C?
Thanks!
Nick
On Monday, June 30,
Without special handling, any 32-bit Windows process is limited to a 2GB
user address space. Due to fragmentation during allocation, you'll never
reach a full 2GB.
On Mon, Jun 30, 2014 at 10:31 AM, Nick Eubank wrote:
> Hi All,
>
> I'm a social scientist wrestling with SQLite in Windows 8 (throu
Hi All,
I'm a social scientist wrestling with SQLite in Windows 8 (through R using
the RSQLite library) for some data manipulation and querying.
No matter what I do to cache_size (or R's memory settings), SQLite never
seems to be using more than about ~1900 mb of RAM. Is that a result of the
32 b
On Mon, Jun 30, 2014 at 9:37 AM, Eleytherios Stamatogiannakis <
est...@gmail.com> wrote:
> Thank you for the answer as well as the merge-join complexity remark. What
> about the union-all with ordered input and an order-by on the whole query?
> Does SQLite use a "merge" algorithm for that case?
>
Thank you for the answer as well as the merge-join complexity remark.
What about the union-all with ordered input and an order-by on the whole
query? Does SQLite use a "merge" algorithm for that case?
Kind regards,
l.
On 26/06/14 21:45, Richard Hipp wrote:
On Thu, Jun 26, 2014 at 11:41 AM
Hi,
I am trying to build sqlite 3.8.5 for vxWorks 6.9 and I'm after a bit of help.
To be more precise, I'm building an RTP for 64bit NEHALEM on vxWorks 6.9.3
Straight out of the box it won't build, I get the following errors
sqlite3.c:24997: error: expected specifier-qualifier-list before 'sem_
JDBC does not support savepoints from SQLite
is there any replacement for savepoints?
if not what to use for bulk inserts to ensure the possibility of rolling
back without losing much data?
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/JDBC-and-savepoints-tp76304.html
S
On Tue, 24 Jun 2014 22:06:15 -0700
Jerry Krinock wrote:
> > The most likely explanation is that it got processed by something
> > which thought it should be treated as ASCII text and was doing a
> > spurious LF-to-CR translation. If there was only one 0x0A byte in
> > the "good" file, then that i
On Tue, 24 Jun 2014 21:02:22 +0100
"Dave Wellman" wrote:
> 2) Assuming that my processing follows this pattern: empty table
> T1 completely, insert a number of rows, insert/select from T1 into
> T2. On the 'select' processing will the 'rowid'
> ** always ** start at 1?
http://www.schemaman
On 2014/06/30 10:30, Hadashi, Rinat wrote:
I work with a very big table, on Linux.
I fail to create index getting the following error:
SQL error near line 1: database or disk is full
Any advice?
Hi Rinat - I was going to simply say "Get a bigger harddrive?" with a smile attached. Obviously yo
On 06/30/2014 03:30 PM, Hadashi, Rinat wrote:
I work with a very big table, on Linux.
I fail to create index getting the following error:
SQL error near line 1: database or disk is full
A CREATE INDEX on a large table uses temporary files to sort the data
before creating the actual index b-tre
I work with a very big table, on Linux.
I fail to create index getting the following error:
SQL error near line 1: database or disk is full
Any advice?
Rinat Hadashi
-
Intel Israel (74) Limited
This e-mail and any attachments
Renji Panicker wrote to this fine list:
>
>- As per the sqlite3PagerOpen function, the size of the memory allocated to
>this pointer is ROUND8(pVfs->szOsFile).
What configuration you're using, Renji?
On some OS/browser/SupportSoftware etc. combinations this function may crash
https://crash-stats
29 matches
Mail list logo