Re: [sqlite] Import feature requests

On Sun, Dec 13, 2009 at 10:31:20PM -0800, Roger Binns wrote > Hint: If you feel the need to get aggressive and abusive when > posting then you probably missed something! If SQLite was useless, > someone else would have noticed by now. I apologize for coming across that way; I din't intend

Re: [sqlite] Import feature requests

Simon Slavin wrote: > On 14 Dec 2009, at 5:13am, Walter Dnes wrote: > > >> The following might be options (compile time, config file, set manually; >> I don't care), but they should be available... >> > > It might be worth writing a separate sqlite3 import facility which just reads > a

Re: [sqlite] Import feature requests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > It might be worth writing a separate sqlite3 import facility which just reads > a .csv into a table. I betcha did not know there are at least 4 different implementations of CSV as a virtual table (2 in the wiki, one in the

Re: [sqlite] Import feature requests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Walter Dnes wrote: > 1) import with strict typing. If I create a table with 3 numeric (real. > integer, whatever) fields, then a CSV file containing... > >2.345, 42, 27.7 > > should import as 3 numbers, not as 3 character strings What makes

Re: [sqlite] Import feature requests

On 14 Dec 2009, at 5:13am, Walter Dnes wrote: > The following might be options (compile time, config file, set manually; > I don't care), but they should be available... It might be worth writing a separate sqlite3 import facility which just reads a .csv into a table. It could have some

[sqlite] Import feature requests

The following might be options (compile time, config file, set manually; I don't care), but they should be available... 1) import with strict typing. If I create a table with 3 numeric (real. integer, whatever) fields, then a CSV file containing... 2.345, 42, 27.7 should import as 3