From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ob-sqlite.el, -init doesn't work with some options
Date: Tue, 09 Nov 2010 13:29:27 -0700 [thread overview]
Message-ID: <87eiaujl5k.fsf@gmail.com> (raw)
In-Reply-To: <87zktigv3t.fsf@dasa3.iem.pw.edu.pl> ("Łukasz Stelmach"'s message of "Tue, 09 Nov 2010 20:22:46 +0100")
Hi Łukasz,
Thanks for mentioning this issue and for posting a workaround.
Would you suggest a different method of passing the body of a sqlite
code block to the sqlite command? The only other options which
immediately occurs to me would involve =cat='ing the body of the code
block through a pipe to the sqlite command (which would probably only
work on unix systems).
Thanks -- Eric
Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
> Hello.
>
> ob-sqlite.el uses -init option to provide sqlite with a src block
> content, however, this prevetns sevarl options' from taking an
> effect. Particularly -header (and it's opposite), -csv and -header
> Create a database, put a SELECT into a file and compare the effects of
> the following commands
>
> sqlite3 -init file.sql -header -separator ';' -csv db.sqlite
>
> cat file.sql | sqlite3 -header -separator ';' -csv db.sqlite
>
> A walkaround is to place desired configration commands (the onse
> beginning with a dot in sqlite) in the src block, e.g:
>
> #+BEGIN_SRC sqlite :db passwords.sqlite :results replace
> .separator |
> .mode csv
> select * from myusers;
> #+END_SRC
next prev parent reply other threads:[~2010-11-09 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 19:22 [BUG] ob-sqlite.el, -init doesn't work with some options Łukasz Stelmach
2010-11-09 20:29 ` Eric Schulte [this message]
2010-11-10 19:45 ` Łukasz Stelmach
2010-11-10 21:03 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiaujl5k.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).