On 19 Dec 2011, at 7:04pm, Tal Tabakman wrote:
> 1. I am using version 3.3.6 of sqlite.
>
> 2. My journal mode is memory
>
> 3. I am opening a transaction and then do 5 inserts before
> committing and opening a new transaction
>
>
> given the above, what are the requirnments (disk-wise)
Hi Simon,
thanks for the response below.
as for your questions:
1. I am using version 3.3.6 of sqlite.
2. My journal mode is memory
3. I am opening a transaction and then do 5 inserts before
committing and opening a new transaction
given the above, what are the requirnments (disk-wise)
On 13 Dec 2011, at 8:10pm, Tal Tabakman wrote:
> I discovered that the problem was not in the index creation but in the
> database creation.
>
> it seems that during DB creation, a certain commit failed due to Disk
> quota and after that indexing failed.
I assume that SQLite did actually
Hi Dan,
thanks for the tips.
the strace tip did the trick.
I discovered that the problem was not in the index creation but in the
database creation.
it seems that during DB creation, a certain commit failed due to Disk
quota and after that indexing failed.
strangely I don't understand this
On Fri, Dec 9, 2011 at 4:02 AM, Tal Tabakman wrote:
> Hi Guys,
> I have an SQLITE database of 1.5 million rows in a single table
> each raw looks like:
>
> 149|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1|
>
> now, from the sqlite command line interface I am
On 12/10/2011 06:01 AM, Tal Tabakman wrote:
Hi,
thanks for the reply.
so, I don't have TMPDIR defined in my env. what is the behaviour of
sqlite in such cases ? is there a default ?
By default it will try /var/tmp, then /usr/tmp, then /tmp.
SQLite creates temporary files there that it uses
On 10 Dec 2011, at 1:23am, Pavel Ivanov wrote:
>> so, I can see the journal file in my work directory which I own (and
>> in which the db file is placed).
>>
>> still constantly, I have a disk I/O ERROR which I don't understand.
>
> If you see journal file along your database file and each
> so, I can see the journal file in my work directory which I own (and
> in which the db file is placed).
>
> still constantly, I have a disk I/O ERROR which I don't understand.
If you see journal file along your database file and each attempt to
open database doesn't delete journal file it means
Hi,
thanks a lot.
so, I can see the journal file in my work directory which I own (and
in which the db file is placed).
still constantly, I have a disk I/O ERROR which I don't understand.
the db is only 64M on disk and I have plenty of space.
how can I get to the bottom of this ?
can it be
On 9 Dec 2011, at 11:01pm, Tal Tabakman wrote:
> so, I don't have TMPDIR defined in my env. what is the behaviour of
> sqlite in such cases ? is there a default ?
The journal file will be created in the same directory as the database file.
For this to work, your application and user must have
Hi,
thanks for the reply.
so, I don't have TMPDIR defined in my env. what is the behaviour of
sqlite in such cases ? is there a default ?
cheers
Tal
On 12/09/2011 04:02 PM, Tal Tabakman wrote:
>* Hi Guys,*>* I have an SQLITE database of 1.5 million rows in a single
>table*>* each raw looks
On 9 Dec 2011, at 9:02am, Tal Tabakman wrote:
> CREATE INDEX IND1 ON ENTRIES (snum)
>
> the result I get is:
>
> Error: disk I/O error
>
> can you advice how to debug this one ?
Before your 'CREATE INDEX' command try typeing
.stats ON
It may or may not do something, depending on which
On 12/09/2011 04:02 PM, Tal Tabakman wrote:
Hi Guys,
I have an SQLITE database of 1.5 million rows in a single table
each raw looks like:
149|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1|
now, from the sqlite command line interface I am creating an on a sincle
integer column
CREATE
Hi Guys,
I have an SQLITE database of 1.5 million rows in a single table
each raw looks like:
149|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1|
now, from the sqlite command line interface I am creating an on a sincle
integer column
CREATE INDEX IND1 ON ENTRIES (snum)
the result I get
14 matches
Mail list logo