-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/01/12 20:45, Antony wrote:
> Did I miss any arguments in the ".dump" command to dump the database
> successfully?
Putting aside the wisdom of structuring a table this way, you did indeed
hit a problem in the SQLite code to dump a table. The
On 28 Jan 2012, at 3:31pm, Alexey Pechnikov wrote:
> 2012/1/28 Simon Slavin :
>> If this database is for longterm use, you're doing the wrong thing. Those
>> should be different rows, not all one huge long row. If it's a one-off
>> hack, then do it and get rid of it
of SQLite Database
Subject: EXT :Re: [sqlite] [sqlite 3.6.22] database ".dump" function cannot
export table of large number of columns < 2000
2012/1/28 Simon Slavin <slav...@bigfraud.org>:
> If this database is for longterm use, you're doing the wrong thing. Those
> should
2012/1/28 Simon Slavin :
> If this database is for longterm use, you're doing the wrong thing. Those
> should be different rows, not all one huge long row. If it's a one-off hack,
> then do it and get rid of it before anyone else sees it and shames you.
Why not? Please
On 28 Jan 2012, at 4:45am, Antony wrote:
> |CREATE TABLE trace1001_constructs (
>id INTEGER NOT NULL,
>tr FLOAT,
>tr0001 FLOAT,
>tr0002 FLOAT,
If this database is for longterm use, you're doing the wrong thing. Those
should be different rows, not all one
I have a table in my sqlite3 database that stores 1001 float numbers in
1001 columns. I wish to dump the database to ascii format for backup
purposes, and I expect the ".dump" function will create a snapshot of
the database.
However, I didn't find any rows of data in the table after
6 matches
Mail list logo