On Fri, Jan 16, 2009 at 09:43:36AM +0100, Christophe Leske wrote:
> sqlite> .o cl1.sql
^^
This says: send output of queries to a file called "cl1.sql".
> sqlite> .dump cl1%
And this says: dump the named table.
> sqlite> select * from cl1;
And the output of this will still go
> After you complete your ".dump" do:
>
> .output stdout
>
Ok, that was stupid, my apologies.
Yet somehow this used to work i think...
Still, when rereading the dumped table, it does not reread the values
correctly for the rtree table.
I am sorry, I must go now, I can provide further in
On Jan 16, 2009, at 3:42 AM, Christophe Leske wrote:
>
>> Try instead:
>>
>>.dump cl1%
> Apparently, this doesn´t help either. Once I tried to export the
> table, the application refuses to show the entries in the table.
>
> The database i am opening here is correct, it holds data in cl1
On Jan 16, 2009, at 3:43 AM, Christophe Leske wrote:
>
> Do you want me to mail you the corrupted database for further
> inspection? I also understand that this is not the right place for
> bugreports eventually.
No. Email me the original, uncorrupted database and instructions for
how to make
> Try instead:
>
> .dump cl1%
Apparently, this doesn´t help either. Once I tried to export the table, the
application refuses to show the entries in the table.
The database i am opening here is correct, it holds data in cl1 prior to
opening it for this step here:
Microsoft Windows XP [Ver
Jim Dodgen schrieb:
> I'm a strong believer in the "continuous improvement" philosophy. Keep up
> the good work.
>
Same here. Better fix stuff as you know of it.
Please keep up the great work with SQlite, i never used such a good and
sturdy tool that just did what it was supposed to do.
I th
Hello!
В сообщении от Thursday 15 January 2009 20:07:49 D. Richard Hipp написал(а):
> All this is to say that we believe that SQLite version 3.6.10 is the
> most stable, most thoroughly tested, and bug-free version of SQLite
> that has ever existed. Please do not be freaked out by three releas
Hello!
В сообщении от Friday 16 January 2009 00:16:43 Thomas Hertweck написал(а):
> It would not make sense to delay bug fixes, but have you ever thought
> about using a different version number scheme? In the Linux kernel
> development
Linux kernel versions compability is bad and so version numb
> Try instead:
>
> .dump cl1%
Apparently, this doesn´t help either. Once I tried to export the table,
the application refuses to show the entries in the table.
The database i am opening here is correct, it holds data in cl1 prior to
opening it for this step here:
Microsoft Windows XP [Vers
On Jan 16, 2009, at 4:27 AM, Nicolas Williams wrote:
> On Thu, Jan 15, 2009 at 10:07:29AM -0800, Brown, Daniel wrote:
>> The frequent releases are not a problem as far as I am concerned.
>> I'd
>> rather have bugs fixed quickly when they are discovered, than wait
>> months for releases contain
Please keep up the great work. I appreciate your fixing major,
identified bugs as fast as possible.
Bob Cochran
D. Richard Hipp wrote:
> SQLite version 3.6.10 is now available on the website. Upgrading is
> recommended for all users.
>
> http://www.sqlite.org/
> http://www.sqlite.org/
On Thu, Jan 15, 2009 at 10:07:29AM -0800, Brown, Daniel wrote:
> The frequent releases are not a problem as far as I am concerned. I'd
> rather have bugs fixed quickly when they are discovered, than wait
> months for releases containing needed fixes like other libraries. We
> use the loose pre-ge
D. Richard Hipp wrote:
> [...]
> Some concern has been expressed that we are releasing too frequently.
> (Three releases in one week is a lot!) The concern is that this
> creates the impression of volatility and unreliability. We have been
> told that we should delay releases in order to cre
D. Richard Hipp wrote:
> All this is to say that we believe that SQLite version 3.6.10 is the
> most stable, most thoroughly tested, and bug-free version of SQLite
> that has ever existed. Please do not be freaked out by three releases
> occurring in one week.
>
Not freaked out at all. Rele
D. Richard Hipp wrote:
SNIP
> Some concern has been expressed that we are releasing too frequently.
> (Three releases in one week is a lot!) The concern is that this
> creates the impression of volatility and unreliability.
SNIP
Most software releases have a few latent bugs within them.
O
Good morning list,
Has anyone else noticed significant memory savings when using larger
page sizes since upgrading to 3.6.9 or 3.6.10 (we were on 3.6.1
previously)? We use about 7.32 MB (Peak 9.64 MB) when loading our
database into RAM using default settings and using larger page sizes
(PRAGMA pa
it through our unit tests.
>
> Daniel
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Mike McGonagle
> Sent: Thursday, January 15, 2009 9:57 AM
> To: General Discussion of SQLite Database
> Subject: Re: [
AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] SQLite version 3.6.10
Thank you for these releases, I appreciate (and agree) with your
reasons for the many releases. For me, it really is so simple that all
I do is take the Amalgamated version and swap it out for the previous
versi
On Jan 15, 2009, at 12:43 PM, Christophe Leske wrote:
> Hi,
>
> if my findings are not mistaken, then the commandline executable of
> the
> new version has some serious problems:
>
> I have a database (which seems correct so far) from which I would like
> to dump a table called "cl1" which is a
Thank you for these releases, I appreciate (and agree) with your
reasons for the many releases. For me, it really is so simple that all
I do is take the Amalgamated version and swap it out for the previous
version. I can only think that anyone who has troubles with a swap
like this may be doing thi
Hi,
if my findings are not mistaken, then the commandline executable of the
new version has some serious problems:
I have a database (which seems correct so far) from which I would like
to dump a table called "cl1" which is a virtual table using an rtree:
sqlite> .o cl1.sql
sqlite> .d cl1
sqli
I wholly agree that release frequency should mirror the frequency of
serious bugs and their fixes. SQLite3 rarely has serious bugs. Two in
one week (one dating to a much earlier version) is out of the ordinary
for SQLite3, but not particularly worrisome.
And agree with your comments about testin
SQLite version 3.6.10 is now available on the website. Upgrading is
recommended for all users.
http://www.sqlite.org/
http://www.sqlite.org/news.html
http://www.sqlite.org/download.html
SQLite version 3.6.10 fixes a cache coherency bug (Ticket #3584)
introduced by check-in [5864]
23 matches
Mail list logo
