Hi,
> I also did another experiment. I created this table and did a vaccum and then
> the select count(*) in sqlite3 was around 2 mins.
>
> When I create an index manually after the table is loaded (imported from
> csv), select count(*) in sqlite3 was within 30 to 40 secs.
>In the second case
Hello,
My Process.csv is around 27G. I've gzipped it and put at
ftp://navinps:sqlit...@h2.usa.hp.com as process.csv.gz
There is only 1 file there.
md5sum process.csv.gz
e77a322744a26d4c8a1ad4d61a84ee72 process.csv.gz
[root@centosnavin sqlite-autoconf-3080801]# cat sqlite3commands.txt
CREATE
Repost: Since it didn't get into the archives or in the mailing list. Sorry
about that.
Quoted and replied to simon after [Repost End]
Hello,
[Repost Begin]
My Process.csv is around 27G. I've gzipped it and put at
ftp://navinps:sqlit...@h2.usa.hp.com as process.csv.gz
There is only 1 file
Hello,
I've few questions about sqlite3 , the database it creates. Actually I'm
finding lot of differences in performance.
My story:
I have this sqlite3 database called hp.db which is like 100+ million
records for table1. The size of hp.db on Linux x64 (CentOS 7) is like 16 GB.
Wh
4 matches
Mail list logo