Hi everybody,
While testing some database upgrade function of mine, I ran into a
segmentation fault. I started looking at the possible cause in my
code, but I soon realized the crash would only happen using SQLite
3.7.7 or 3.7.8. If I use 3.7.6 or lower, things go safely.
Since I am not familiar
On 10/29/2011 03:00 PM, Alexandre Courbot wrote:
Hi everybody,
While testing some database upgrade function of mine, I ran into a
segmentation fault. I started looking at the possible cause in my
code, but I soon realized the crash would only happen using SQLite
3.7.7 or 3.7.8. If I use 3.7.6
Yes, compiling to 32-bit is nice. It is like dancing at the tunes of "Earth
Wind and Fire", h, those were the days. Like the old good songs, the
32bit apps are a good memory, many people like it, but they are a thing of
the past. We are developers and anyone of us who stays behind, is left
Dan,
On Sat, Oct 29, 2011 at 8:48 PM, Dan Kennedy wrote:
> Found one problem:
>
> Ticket: http://www.sqlite.org/src/info/48f299634a
> Fix: http://www.sqlite.org/src/info/3565fcf898
>
> Please follow up if you try this fix and you still get
> the crash.
Thanks for
By the way, can we expect a point release (3.7.8.1?) that includes
this fix soon? It seems rather serious to me, and the use case should
not be so seldom.
Alex.
___
sqlite-users mailing list
sqlite-users@sqlite.org
I have 64-bit binary package for my OS (kindly maintained by guy named
Panu Matilainen, outside of the sqltie.org core team).
I have installed this package after the command: yum install sqlite This
currently installs 3.7.5 for me.
If I want to test/use different version I type: fossill
On Sat, Oct 29, 2011 at 8:40 AM, Alexandre Courbot wrote:
> By the way, can we expect a point release (3.7.8.1?) that includes
> this fix soon? It seems rather serious to me, and the use case should
> not be so seldom.
>
The fix will be in 3.7.9.
--
D. Richard Hipp
As a programmer, I just build my own 64 bit version of Sqlite. You
should try it, it's easy. Just a matter of selecting "x64" when I
compile.
For my customers, 64 bit installs now outnumber 32 bit. Sqlite works
just fine...
C
Saturday, October 29, 2011, 8:03:55 AM, you wrote:
AO>
I have a table with one TEXT column. I insert 1 million rows of short
strings, and then create an UNIQUE INDEX. The speed is very acceptable. Then
I insert another 10.000 short strings, and the performance is very bad, it
almosts take longer than inserting the initial million(!) rows to fill the
On 29 Oct 2011, at 5:57pm, Fabian wrote:
> I have a table with one TEXT column. I insert 1 million rows of short
> strings, and then create an UNIQUE INDEX. The speed is very acceptable. Then
> I insert another 10.000 short strings, and the performance is very bad, it
> almosts take longer than
2011/10/29 Simon Slavin
>
> When you insert the 10,000 strings are you doing it inside a transaction ?
>
> BEGIN TRANSACTION;
> INSERT ...
> INSERT ...
> INSERT ...
> COMMIT;
>
>
Yes, I use transactions, prepared statements, cache_size, journal_mode and
synchronous
11 matches
Mail list logo