Re: [sqlite] Data loss after vacuum

[Simon Slavin]

On 2 Nov 2009, at 6:39pm, chen jia wrote:

> Thanks for your replies, Simon and Dair.
>
> Yes, it is probably a bug in sqlite version 3.6.10.  After I upgraded
> to version 3.6.12, I ran vacuum again and had no problems.

That's good news.

> I do have more questions.
>
> I want to clean fragmentation in the database with vacuum command.
>
> When I ran a combination of '.dump' and '.read' commands to create a
> new database, for example, $sqlite3 hq.db '.dump' | sqlite3 hq_new.db,
> does it achieve the same thing as vacuum does?

I don't think there would be much difference between the two resulting  
database files.

> If yes, what's the
> advantage of vaccum? Thanks.

You can call VACUUM from your own program, as a SQL command.  It would  
be much faster than dumping to text and reading the text file again.   
There is no easy way to dump a database to a text file inside your own  
program unless you can call the sqlite3 command-line tool.

On the other hand, if you are trying to ensure that your data is  
readable by many applications, or to compress your data to the  
smallest file, the ability of the command-line tool to produce a text  
file is extremely useful.  And just in case your database is corrupt  
in some way, dumping the data as text is more likely to get rid of  
corruption.

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Data loss after vacuum

[chen jia]

Thanks for your replies, Simon and Dair.

Yes, it is probably a bug in sqlite version 3.6.10.  After I upgraded
to version 3.6.12, I ran vacuum again and had no problems.

I do have more questions.

I want to clean fragmentation in the database with vacuum command.

When I ran a combination of '.dump' and '.read' commands to create a
new database, for example, $sqlite3 hq.db '.dump' | sqlite3 hq_new.db,
does it achieve the same thing as vacuum does?  If yes, what's the
advantage of vaccum? Thanks.

Best,
Jia



On Sat, Oct 31, 2009 at 5:55 PM, Dair Grant  wrote:
> chen jia wrote:
>
>> Before I ran vacuum, I ran pragma integrity_check; and got
>> sqlite> pragma integrity_check;
>> ok
>>
>> After I ran vacuum, I ran pragma integrity_check; again and got
>> sqlite> pragma integrity_check;
>> *** in database main ***
>> On tree page 15 cell 36: Child page depth differs
>> On tree page 15 cell 37: Child page depth differs
>> On tree page 20 cell 1: Child page depth differs
>
> This sounds like an issue I ran into:
>
>  
>
> I sent some test cases to DRH to examine and he indicated the bug was
> present in 3.6.10 but was fixed in 3.6.11.
>
>
> -dair
> ___
> d...@refnum.com              http://www.refnum.com/
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
 Ohio State University - Finance
   248 Fisher Hall
2100 Neil Ave.
  Columbus, Ohio  43210
 Telephone: 614-292-2979
   http://www.fisher.osu.edu/~chen_1002/
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Data loss after vacuum

[Dair Grant]

chen jia wrote:

> Before I ran vacuum, I ran pragma integrity_check; and got
> sqlite> pragma integrity_check;
> ok
> 
> After I ran vacuum, I ran pragma integrity_check; again and got
> sqlite> pragma integrity_check;
> *** in database main ***
> On tree page 15 cell 36: Child page depth differs
> On tree page 15 cell 37: Child page depth differs
> On tree page 20 cell 1: Child page depth differs

This sounds like an issue I ran into:

  

I sent some test cases to DRH to examine and he indicated the bug was
present in 3.6.10 but was fixed in 3.6.11.


-dair
___
d...@refnum.com  http://www.refnum.com/


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Data loss after vacuum

[Simon Slavin]

On 31 Oct 2009, at 9:39pm, chen jia wrote:

> I have not updated sqlite from version 3.6.10 to version 3.6.12 yet.

3.6.10 was January 2009.  9 months ago.  Perhaps there's an easy way  
to get a later version.

> But, I have tried .dump by following the instructions on
> .
>
> I created a new database by using
> $ echo '.dump' | sqlite3 hq.db | gzip -c > hq.dump.gz

Unzip the .gz file into a text file and look through it.  See if you  
can see anything strange about it, especially in table firmsret11.  I  
will bet that it looks okay.

> $ zcat hq.dump.gz | sqlite3 hq3.db
>
> Then, I did pragma integrity_check and vacuum on the new database.
> Before I ran vacuum, the pragma integrity check returns OK. After I
> ran vacuum, I still got errors when I ran pragma integrity_check.
> Also, the number of rows of table firmsret11 reduces to 2.

I think you have come up against one of the known bugs in 3.6.10.  But  
I don't know enough about SQLite to be sure.  However, I'd recommend  
you update just in case the bug I'm thinking of, or a later bug is  
causing your problem.  And anyone trying to cure your bug will  
definitely want to start from the current version of SQLite, not one  
nine months old.

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Data loss after vacuum

[chen jia]

> Although the first integrity_check says that there are no errors, it
> may be wrong.  I am not able to definitely tell what is wrong, so I am
> just guessing.  Your earlier post said you were running version
> 3.6.10.  Please try to update to the latest version of SQLite
> available for your platform, but at least version 3.6.12.
>
> You may wish to rescue as much data as possible out of your database
> file.  One way to do this is to open it in the command-line tool and
> use the '.dump' command to create a text file with the SQL commands in
> to recreate the database.  You can then create a new blank database
> file and use the '.read' command to run those SQL commands to make a
> new, uncorrupt database which /should/ have all your data in.  Please
> see the page
>
> 
>
> for examples of how to write output to a text file but one example
> would be
>
> echo '.dump' | sqlite3 hq.db > hq.txt
>
> You should be able to use VACUUM on the new database file without any
> problems.
>
> Simon.
>
> PS: Please allow replies to go to the mailing list as normal.  That
> way if one person gives you bad advice another person can see it and
> correct it.

Thanks again, Simon,

I am using ubuntu 9.04. I installed sqlite3 by using apt-get install
sqlite3 and got sqlite3 version 3.6.10.

I have not updated sqlite from version 3.6.10 to version 3.6.12 yet.
But, I have tried .dump by following the instructions on
.

I created a new database by using
$ echo '.dump' | sqlite3 hq.db | gzip -c > hq.dump.gz
$ zcat hq.dump.gz | sqlite3 hq3.db

Then, I did pragma integrity_check and vacuum on the new database.
Before I ran vacuum, the pragma integrity check returns OK. After I
ran vacuum, I still got errors when I ran pragma integrity_check.
Also, the number of rows of table firmsret11 reduces to 2.

$ sqlite3 hq3.db
SQLite version 3.6.10
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> pragma integrity_check;
ok
sqlite> vacuum;
sqlite> select count(*) from firmsret11;
2
sqlite> pragma integrity_check;
*** in database main ***
On tree page 19 cell 20: Child page depth differs
On tree page 19 cell 21: Child page depth differs
On tree page 3301422 cell 103: Child page depth differs
On tree page 16011 cell 0: 2nd reference to page 15965
On tree page 16011 cell 1: 2nd reference to page 15966
On tree page 16011 cell 2: 2nd reference to page 15967
On tree page 16011 cell 3: 2nd reference to page 15968
On tree page 16011 cell 4: 2nd reference to page 15969
On tree page 16011 cell 5: 2nd reference to page 15970
On tree page 16011 cell 6: 2nd reference to page 15971
On tree page 16011 cell 7: 2nd reference to page 15972
On tree page 16011 cell 8: 2nd reference to page 15973
On tree page 16011 cell 9: 2nd reference to page 15974
On tree page 16011 cell 10: 2nd reference to page 15975
On tree page 16011 cell 11: 2nd reference to page 15976
On tree page 16011 cell 12: 2nd reference to page 15977
On tree page 16011 cell 13: 2nd reference to page 15978
On tree page 16011 cell 14: 2nd reference to page 15979
On tree page 16011 cell 15: 2nd reference to page 15980
On tree page 16011 cell 16: 2nd reference to page 15981
On tree page 16011 cell 17: 2nd reference to page 15982
On tree page 16011 cell 18: 2nd reference to page 15983
On tree page 16011 cell 19: 2nd reference to page 15984
On tree page 16011 cell 20: 2nd reference to page 15985
On tree page 16011 cell 21: 2nd reference to page 15986
On tree page 16011 cell 22: 2nd reference to page 15987
On tree page 16011 cell 23: 2nd reference to page 15988
On tree page 16011 cell 24: 2nd reference to page 15989
On tree page 16011 cell 25: 2nd reference to page 15990
On tree page 16011 cell 26: 2nd reference to page 15991
On tree page 16011 cell 27: 2nd reference to page 15992
On tree page 16011 cell 28: 2nd reference to page 15993
On tree page 16011 cell 29: 2nd reference to page 15994
On tree page 16011 cell 30: 2nd reference to page 15995
On tree page 16011 cell 31: 2nd reference to page 15996
On tree page 16011 cell 32: 2nd reference to page 15997
On tree page 16011 cell 33: 2nd reference to page 15998
On tree page 16011 cell 34: 2nd reference to page 15999
On tree page 16011 cell 35: 2nd reference to page 16000
On tree page 16011 cell 36: 2nd reference to page 16001
On tree page 16011 cell 37: 2nd reference to page 16002
On tree page 16011 cell 38: 2nd reference to page 16003
On tree page 16011 cell 39: 2nd reference to page 16004
On tree page 16011 cell 40: 2nd reference to page 16005
On tree page 16011 cell 41: 2nd reference to page 16006
On tree page 16011 cell 42: 2nd reference to page 16007
On tree page 16011 cell 43: 2nd reference to page 16008
On tree page 16011 cell 44: 2nd reference to page 16009
On tree page 16011 cell 45: 2nd reference to page 16010
On tree page 16011 cell 46: 2nd reference to page 16012
On tree page 16011 cell 47: 2nd reference to page 16013
On tree page 16011 cel

Re: [sqlite] Data loss after vacuum

[Simon Slavin]

On 31 Oct 2009, at 7:03pm, chen jia wrote:

> Before I ran vacuum, I ran pragma integrity_check; and got
> sqlite> pragma integrity_check;
> ok
>
> After I ran vacuum, I ran pragma integrity_check; again and got
> sqlite> pragma integrity_check;
> *** in database main ***
> On tree page 15 cell 36: Child page depth differs
> On tree page 15 cell 37: Child page depth differs
> On tree page 20 cell 1: Child page depth differs
> On tree page 3301422 cell 103: Child page depth differs
> On tree page 13623 cell 0: 2nd reference to page 13592
> On tree page 13623 cell 1: 2nd reference to page 13593

Although the first integrity_check says that there are no errors, it  
may be wrong.  I am not able to definitely tell what is wrong, so I am  
just guessing.  Your earlier post said you were running version  
3.6.10.  Please try to update to the latest version of SQLite  
available for your platform, but at least version 3.6.12.

You may wish to rescue as much data as possible out of your database  
file.  One way to do this is to open it in the command-line tool and  
use the '.dump' command to create a text file with the SQL commands in  
to recreate the database.  You can then create a new blank database  
file and use the '.read' command to run those SQL commands to make a  
new, uncorrupt database which /should/ have all your data in.  Please  
see the page



for examples of how to write output to a text file but one example  
would be

echo '.dump' | sqlite3 hq.db > hq.txt

You should be able to use VACUUM on the new database file without any  
problems.

Simon.

PS: Please allow replies to go to the mailing list as normal.  That  
way if one person gives you bad advice another person can see it and  
correct it.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Data loss after vacuum

[chen jia]

> Please enter this line in the same sqlite3 tool you are using for
> vacuum:

> PRAGMA integrity_check;

> It appears that you have a copy of the database from before the
> 'vacuum' command.  If you can, take another copy and run the PRAGMA
> command both before and after the 'vacuum'.  For more details see

> 

> Simon.

Thanks, Simon,

Before I ran vacuum, I ran pragma integrity_check; and got
sqlite> pragma integrity_check;
ok

After I ran vacuum, I ran pragma integrity_check; again and got
sqlite> pragma integrity_check;
*** in database main ***
On tree page 15 cell 36: Child page depth differs
On tree page 15 cell 37: Child page depth differs
On tree page 20 cell 1: Child page depth differs
On tree page 3301422 cell 103: Child page depth differs
On tree page 13623 cell 0: 2nd reference to page 13592
On tree page 13623 cell 1: 2nd reference to page 13593
On tree page 13623 cell 2: 2nd reference to page 13594
On tree page 13623 cell 3: 2nd reference to page 13595
On tree page 13623 cell 4: 2nd reference to page 13596
On tree page 13623 cell 5: 2nd reference to page 13597
On tree page 13623 cell 6: 2nd reference to page 13598
On tree page 13623 cell 7: 2nd reference to page 13599
On tree page 13623 cell 8: 2nd reference to page 13600
On tree page 13623 cell 9: 2nd reference to page 13601
On tree page 13623 cell 10: 2nd reference to page 13602
On tree page 13623 cell 11: 2nd reference to page 13603
On tree page 13623 cell 12: 2nd reference to page 13604
On tree page 13623 cell 13: 2nd reference to page 13605
On tree page 13623 cell 14: 2nd reference to page 13606
On tree page 13623 cell 15: 2nd reference to page 13607
On tree page 13623 cell 16: 2nd reference to page 13608
On tree page 13623 cell 17: 2nd reference to page 13609
On tree page 13623 cell 18: 2nd reference to page 13610
On tree page 13623 cell 19: 2nd reference to page 13611
On tree page 13623 cell 20: 2nd reference to page 13612
On tree page 13623 cell 21: 2nd reference to page 13613
On tree page 13623 cell 22: 2nd reference to page 13614
On tree page 13623 cell 23: 2nd reference to page 13615
On tree page 13623 cell 24: 2nd reference to page 13616
On tree page 13623 cell 25: 2nd reference to page 13617
On tree page 13623 cell 26: 2nd reference to page 13618
On tree page 13623 cell 27: 2nd reference to page 13619
On tree page 13623 cell 28: 2nd reference to page 13620
On tree page 13623 cell 29: 2nd reference to page 13621
On tree page 13623 cell 30: 2nd reference to page 13622
On tree page 13623 cell 31: 2nd reference to page 13624
On tree page 13623 cell 32: 2nd reference to page 13625
On tree page 13623 cell 33: 2nd reference to page 13626
On tree page 13623 cell 34: 2nd reference to page 13627
On tree page 13623 cell 35: 2nd reference to page 13628
On tree page 13623 cell 36: 2nd reference to page 13629
On tree page 13623 cell 37: 2nd reference to page 13630
On tree page 13623 cell 38: 2nd reference to page 13631
On tree page 13623 cell 39: 2nd reference to page 13632
On tree page 13623 cell 40: 2nd reference to page 13633
On tree page 13623 cell 41: 2nd reference to page 13634
On tree page 13623 cell 42: 2nd reference to page 13635
On tree page 13623 cell 43: 2nd reference to page 13636
On tree page 13623 cell 44: 2nd reference to page 13637
On tree page 13623 cell 45: 2nd reference to page 13638
On tree page 13623 cell 46: 2nd reference to page 13639
On tree page 13623 cell 47: 2nd reference to page 13640
On tree page 13623 cell 48: 2nd reference to page 13641
On tree page 13623 cell 49: 2nd reference to page 13642
On tree page 13623 cell 50: 2nd reference to page 13643
On tree page 13623 cell 51: 2nd reference to page 13644
On tree page 13623 cell 52: 2nd reference to page 13645
On tree page 13623 cell 53: 2nd reference to page 13646
On tree page 13623 cell 54: 2nd reference to page 13647
On tree page 13623 cell 55: 2nd reference to page 13648
On tree page 13623 cell 56: 2nd reference to page 13649
On tree page 13623 cell 57: 2nd reference to page 13650
On tree page 13623 cell 58: 2nd reference to page 13651
On tree page 13623 cell 59: 2nd reference to page 13652
On tree page 13623 cell 60: 2nd reference to page 13653
On tree page 13623 cell 61: 2nd reference to page 13654
On tree page 13623 cell 62: 2nd reference to page 13655
On tree page 13623 cell 63: 2nd reference to page 13656
On tree page 13623 cell 64: 2nd reference to page 13657
On tree page 13623 cell 65: 2nd reference to page 13658
On tree page 13623 cell 66: 2nd reference to page 13659
On tree page 13623 cell 67: 2nd reference to page 13660
On tree page 13623 cell 68: 2nd reference to page 13661
On tree page 13623 cell 69: 2nd reference to page 13662
On tree page 13623 cell 70: 2nd reference to page 13663
On tree page 13623 cell 71: 2nd reference to page 13664
On tree page 13623 cell 72: 2nd reference to page 13665
On tree page 13623 cell 73: 2nd reference to page 13666
On tree page 13623 cell 74: 2nd reference to page 13667
On tree page

Re: [sqlite] Data loss after vacuum

[chen jia]

> Please enter this line in the same sqlite3 tool you are using for
> vacuum:

> PRAGMA integrity_check;

> It appears that you have a copy of the database from before the
> 'vacuum' command.  If you can, take another copy and run the PRAGMA
> command both before and after the 'vacuum'.  For more details see

> 

> Simon.

Thanks, Simon,

Before I ran vacuum, I ran pragma integrity_check; and got
sqlite> pragma integrity_check;
ok

After I ran vacuum, I ran pragma integrity_check; again and got
sqlite> pragma integrity_check;
*** in database main ***
On tree page 15 cell 36: Child page depth differs
On tree page 15 cell 37: Child page depth differs
On tree page 20 cell 1: Child page depth differs
On tree page 3301422 cell 103: Child page depth differs
On tree page 13623 cell 0: 2nd reference to page 13592
On tree page 13623 cell 1: 2nd reference to page 13593
On tree page 13623 cell 2: 2nd reference to page 13594
On tree page 13623 cell 3: 2nd reference to page 13595
On tree page 13623 cell 4: 2nd reference to page 13596
On tree page 13623 cell 5: 2nd reference to page 13597
On tree page 13623 cell 6: 2nd reference to page 13598
On tree page 13623 cell 7: 2nd reference to page 13599
On tree page 13623 cell 8: 2nd reference to page 13600
On tree page 13623 cell 9: 2nd reference to page 13601
On tree page 13623 cell 10: 2nd reference to page 13602
On tree page 13623 cell 11: 2nd reference to page 13603
On tree page 13623 cell 12: 2nd reference to page 13604
On tree page 13623 cell 13: 2nd reference to page 13605
On tree page 13623 cell 14: 2nd reference to page 13606
On tree page 13623 cell 15: 2nd reference to page 13607
On tree page 13623 cell 16: 2nd reference to page 13608
On tree page 13623 cell 17: 2nd reference to page 13609
On tree page 13623 cell 18: 2nd reference to page 13610
On tree page 13623 cell 19: 2nd reference to page 13611
On tree page 13623 cell 20: 2nd reference to page 13612
On tree page 13623 cell 21: 2nd reference to page 13613
On tree page 13623 cell 22: 2nd reference to page 13614
On tree page 13623 cell 23: 2nd reference to page 13615
On tree page 13623 cell 24: 2nd reference to page 13616
On tree page 13623 cell 25: 2nd reference to page 13617
On tree page 13623 cell 26: 2nd reference to page 13618
On tree page 13623 cell 27: 2nd reference to page 13619
On tree page 13623 cell 28: 2nd reference to page 13620
On tree page 13623 cell 29: 2nd reference to page 13621
On tree page 13623 cell 30: 2nd reference to page 13622
On tree page 13623 cell 31: 2nd reference to page 13624
On tree page 13623 cell 32: 2nd reference to page 13625
On tree page 13623 cell 33: 2nd reference to page 13626
On tree page 13623 cell 34: 2nd reference to page 13627
On tree page 13623 cell 35: 2nd reference to page 13628
On tree page 13623 cell 36: 2nd reference to page 13629
On tree page 13623 cell 37: 2nd reference to page 13630
On tree page 13623 cell 38: 2nd reference to page 13631
On tree page 13623 cell 39: 2nd reference to page 13632
On tree page 13623 cell 40: 2nd reference to page 13633
On tree page 13623 cell 41: 2nd reference to page 13634
On tree page 13623 cell 42: 2nd reference to page 13635
On tree page 13623 cell 43: 2nd reference to page 13636
On tree page 13623 cell 44: 2nd reference to page 13637
On tree page 13623 cell 45: 2nd reference to page 13638
On tree page 13623 cell 46: 2nd reference to page 13639
On tree page 13623 cell 47: 2nd reference to page 13640
On tree page 13623 cell 48: 2nd reference to page 13641
On tree page 13623 cell 49: 2nd reference to page 13642
On tree page 13623 cell 50: 2nd reference to page 13643
On tree page 13623 cell 51: 2nd reference to page 13644
On tree page 13623 cell 52: 2nd reference to page 13645
On tree page 13623 cell 53: 2nd reference to page 13646
On tree page 13623 cell 54: 2nd reference to page 13647
On tree page 13623 cell 55: 2nd reference to page 13648
On tree page 13623 cell 56: 2nd reference to page 13649
On tree page 13623 cell 57: 2nd reference to page 13650
On tree page 13623 cell 58: 2nd reference to page 13651
On tree page 13623 cell 59: 2nd reference to page 13652
On tree page 13623 cell 60: 2nd reference to page 13653
On tree page 13623 cell 61: 2nd reference to page 13654
On tree page 13623 cell 62: 2nd reference to page 13655
On tree page 13623 cell 63: 2nd reference to page 13656
On tree page 13623 cell 64: 2nd reference to page 13657
On tree page 13623 cell 65: 2nd reference to page 13658
On tree page 13623 cell 66: 2nd reference to page 13659
On tree page 13623 cell 67: 2nd reference to page 13660
On tree page 13623 cell 68: 2nd reference to page 13661
On tree page 13623 cell 69: 2nd reference to page 13662
On tree page 13623 cell 70: 2nd reference to page 13663
On tree page 13623 cell 71: 2nd reference to page 13664
On tree page 13623 cell 72: 2nd reference to page 13665
On tree page 13623 cell 73: 2nd reference to page 13666
On tree page 13623 cell 74: 2nd reference to page 13667
On tree page

Re: [sqlite] Data loss after vacuum

[Simon Slavin]

On 31 Oct 2009, at 3:22am, chen jia wrote:

> Before I ran vacuum, this table, firmsret11, has 2338120 rows.
>
> After I ran vacuum as follows,
> $ sqlite3 hq.db
> SQLite version 3.6.10
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> vacuum;
> sqlite> .exit
>
> and this table only had two rows,
> $ sqlite3 hq.db
> SQLite version 3.6.10
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> select count(*) from firmsret11;
> 2
>
> Dose anyone know how this could happen and how I can do to check what
> is causing this problem?  Thanks.

Please enter this line in the same sqlite3 tool you are using for  
vacuum:

PRAGMA integrity_check;

It appears that you have a copy of the database from before the  
'vacuum' command.  If you can, take another copy and run the PRAGMA  
command both before and after the 'vacuum'.  For more details see



Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Data loss after vacuum

[chen jia]

Hi there,

I experienced data loss in one my tables after I execute vacuum
command from sqlite3.

Before I ran vacuum, this table, firmsret11, has 2338120 rows.

After I ran vacuum as follows,
$ sqlite3 hq.db
SQLite version 3.6.10
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> vacuum;
sqlite> .exit

and this table only had two rows,
$ sqlite3 hq.db
SQLite version 3.6.10
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select count(*) from firmsret11;
2

Dose anyone know how this could happen and how I can do to check what
is causing this problem?  Thanks.

Best,
Jia
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users