From: Eric Schulte <email@example.com>
To: Daniel Clemente <firstname.lastname@example.org>
Cc: org-mode Mailinglist <email@example.com>
Subject: Re: sqlite3 in org-babel
Date: Sat, 18 Feb 2012 09:31:30 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Daniel Clemente's message of "Fri, 17 Feb 2012 00:14:21 +0100")
Daniel Clemente <firstname.lastname@example.org> writes:
>> Have you tried using a sqlite code block? See ob-sqlite.el
> I didn't notice there were both ob-sql and ob-sqlite. It would be
> useful to mention sqlite inside ob-sql.
> Perhaps they should be united?
I believe there were reasons for keeping them separate. I'd rather not
combine them without a full overview of both code files.
> I still prefer ob-sql for sqlite because it lets me pass the
> parameter ":init /dev/null". That makes it NOT load my ~/.sqliterc
> (where I have a very verbose ".tables"). ob-sqlite does not have
> ":init" and therefore always stuffs that output into the results.
From looking at the man page of sqlite, it seems you can do the same
with ob-sqlite. Simply pass "--init /dev/null" to the sqlite command.
This could be done e.g. with something like
(org-babel-sqlite3-command "sqlite3 --init /dev/null")
>> Daniel Clemente <email@example.com> writes:
>> > Hi,
>> > org-babel works well with sqlite3 if you add this (which I propose for inclusion):
prev parent reply other threads:[~2012-02-18 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 23:18 sqlite3 in org-babel Daniel Clemente
2012-02-14 14:38 ` [babel][patch] " Martyn Jago
2012-02-15 15:16 ` Eric Schulte
2012-02-16 23:14 ` Daniel Clemente
2012-02-18 16:31 ` Eric Schulte [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).