> -----Original Message----- > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf > Of Richard Hipp > Sent: Thursday, June 27, 2013 7:59 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] sqlite3: .import command handles quotation incorrectly > > On Thu, Jun 27, 2013 at 8:53 AM, Konrad Hambrick <kon...@payplus.com> wrote: > > > > > Hmmm ... I don't believe my patch file went thru ... > > > > Is there an acceptable method to include text files ? > > > > We cannot accept your patch anyhow, unless you have a Contributor License > Agreement on file. To do otherwise would jeopardize the public domain > status of SQLite. > Thanks for the feedback, Richard.
How do I learb more about the Contributor License Agreement ? I don't see it on the WebSite ... > But I am looking into your idea... > > What if, instead of a new command, we simply extend the ".import" command > so that if the first character of the filename is "|" it interprets the > filename as a pipe instead of a file. The ".output" command works that way. > > One downside is that the entire command has to be in a single argument, > which complicates the use of ' and " characters in the command itself. I looked at the |command option for .import before I settled on a new .pimport command but I didn't want to have to mess with the command line arg logic in the do_meta_command( ) function. That's why I opted for the .pimport command instead ... It greatly simplified command line handling -- the Table is in azArg[1] and then I popen the literal line that follows azArg[1] :) -- kjh _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
