emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: Ag Ibragimov <agzam.ibragimov@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-sql src blocks with a totally custom engine
Date: Wed, 17 Jun 2020 07:20:08 +0800	[thread overview]
Message-ID: <87pn9ypphz.fsf@gmail.com> (raw)
In-Reply-To: <m2o8pig34r.fsf@gmail.com>

Hash: SHA256

Ag Ibragimov <agzam.ibragimov@gmail.com> writes:

> Is it possible to have source code SQL blocks that are processed with a custom command line tool?
> e.g. how can I make something like this to work:
> #+begin_src sql :cmdline "osqueryi --json"
>  select * from processes limit 5;
> #+end_src

I think it's possible. Should not be hard to implement. You can check out ob-sql.el source code.

> For those who don't know what osquery is, here's a quote from https://osquery.io: "Osquery uses basic SQL commands to leverage a relational data-model to describe a device."

This is interesting project.

> I vaguely remember there was a way to basically "pipe" entire code block to be executed in a given cmd line tool, but I am struggling to find how to do that. There's a way, right? But even then, I think it requires the code block to be of sh-mode of shell-mode, but I want it to be SQL because osquery uses SQL.

- -- 
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


      reply	other threads:[~2020-06-16 23:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 20:35 ob-sql src blocks with a totally custom engine Ag Ibragimov
2020-06-16 23:20 ` stardiviner [this message]

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:

  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=87pn9ypphz.fsf@gmail.com \
    --to=numbchild@gmail.com \
    --cc=agzam.ibragimov@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).