I have made the test with following results: Useing "SELECT ALL * FROM <tablename> WHERE... order by id;" on the original database and "SELECT ALL * FROM <tablename> order by id;" on the cloned database give me the same results. outputing the results from SELECT in different files give me two 100% identical files. I have used the commandline utility in this case, but the same results shows the SQLite browser too.
ken-33 wrote: > > Doesnt seem like that much data. you could do a sanity check and select > the row counts from each table and use the where clause on the original. > > You could use the .output command selecting the data to different files > (use an order by clause) then compare the two files. > > HTH > > --- On Tue, 8/5/08, csabi81 <[EMAIL PROTECTED]> wrote: > > From: csabi81 <[EMAIL PROTECTED]> > Subject: Re: [sqlite] Clone SQLite databases > To: sqlite-users@sqlite.org > Date: Tuesday, August 5, 2008, 6:42 AM > > Thanks for Reply. > > I have tried VACUUM, nothing happens. The original database file remains > the > same size as before. > What I create in the new database are Tables, Indexes and Triggers as > well. > I dont know if anything escapes from me. > > > Mihai Limbasan wrote: >> >> csabi81 wrote: >>> Hi everyone >>> >>> I want to clone a database: copy all data from original database to > the >>> destination database with a condition, so not all the entries need to > be >>> copied. I have tried the following: >>> Obtain SQL from mastertable and create the tables in the new database, >>> and >>> using INSERT to copy all data with a WHERE. My problem is that the >>> destination file size became very small; original was 160KB the >>> destination >>> is 55KB, I have deleted only a few entries. When I opened each > database >>> with >>> a SQLite Browser it seems everything OK, but I do not understand why > the >>> filesize became so small? >>> Am I loosing something to copy, or create? >>> >>> Tx for any help. >>> >>> P.S> sorry for my english :P >>> >> You might want to try to VACUUM the original database to see whether the >> file size is reduced on it as well. Please read the documentation on the >> VACUUM command here: http://sqlite.org/lang_vacuum.html >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> >> > > -- > View this message in context: > http://www.nabble.com/Clone-SQLite-databases-tp18827472p18829325.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://www.nabble.com/Clone-SQLite-databases-tp18827472p18832398.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users