> I try very hard not to reinvent the wheel You don't have to, just need a different wheel. I did this recently both for .csv and also for .html and working very nicely and far more flexible than using the code in shell.c.
RBS On Wed, Jan 17, 2018 at 10:54 AM, Shane Dev <devshan...@gmail.com> wrote: > On 17 January 2018 at 08:45, petern <peter.nichvolo...@gmail.com> wrote: > > > Shane. Expect to do a lot of hacking on shell.c. It's not intended as a > > library but as the main program of a console application. > > > That's a shame. I try very hard not to reinvent the wheel especially when > the wheel question (shell.c) is widely used, flexible and presumably > thoroughly debugged. > > However, I can't be the only one trying to programmatically exchange data > between SQLite and a delimited text file. For importing, the CSV virtual > table works well for multi-column CSVs, thanks again for the tip. For > exporting, I could retrieve the data using sqlite3_exec and build a string > from the 3rd and 4th parameters of the callback function. Then I would need > to code logic to insert the column and line separators and handle edge > cases (fields containing separators or double quotes, single column tables, > etc) and finally write the string to a file. > > Is this most efficient approach? > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
