csv.c isn't a writer. Shane expected to write the file by inserting rows into the vtable. He has no application whatsoever but for the shell.
Richard, since you're responding to questions, let me ask again about 3.22 INTROPECTION_PRAGMAS release. Will function_list() be progressing at all toward outputing a composite key for the function? What about a module name column in 3.22? Seeing which module currently controls the function name would be a helpful diagnostic at least. Peter On Wed, Jan 17, 2018 at 10:43 AM, Richard Hipp <d...@sqlite.org> wrote: > On 1/17/18, petern <peter.nichvolo...@gmail.com> wrote: > > Take a look at the function shell_callback for hints. > > If the goal is to create a TSV reader/writer, it seems like the CVS > reader/writer might be a better starting point, as it is unencumbered > by lots of other unrelated features as is the shell. You might be > able to get cvs.c to work simply by changing a single instance of a > ',' literal into '\t'. Probably a little more work than that will be > involved, but not too much more. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > 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
