emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: juh <juh+ntg-context@mailbox.org>
To: emacs-orgmode@gnu.org
Cc: Jan Ulrich Hasecke <juh@mailbox.org>
Subject: Re: Tutorials on creating pdfs with org-babel and sqlite
Date: Sun, 13 Nov 2022 13:05:45 +0100	[thread overview]
Message-ID: <Y3DdmQGCSBlU/m3r@odysseus> (raw)
In-Reply-To: <Y3BY0cg8lnavGulf@protected.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

Hi Jean,

thank you very much for your answer,

Am Sun, Nov 13, 2022 at 05:39:13AM +0300 schrieb Jean Louis:
> - use PostgreSQL and its rich features, forget SQLite. Single user
>   single computer database is good for you personally, but modifying
>   tables and developing new features is far harder with SQLite.

I agree with this. I my work we always use it, but this project of mine
is very small, in fact it is nothing more than a collection of song

Perhaps I'll do a little language analysis with NLTK and Python, but
nothing very fancy. 

> - Separate lightweight markup language LWM from publishing objects
>   table. Make the publishing available for any kind of LWM!

This sound very interesting, but goes way beyond my knowledge.

Am I write that this is a tool to reformat the output of a sql query
into the listed LWN? Meaing that if I export the org file to md the
table output eg. is converted to md? I thought that this is done by the
org export mechanism?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-11-13 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 18:06 Tutorials on creating pdfs with org-babel and sqlite Jan Ulrich Hasecke
2022-11-13  0:57 ` Christopher M. Miles
2022-11-13  1:57 ` Vikas Rawal
2022-11-13  2:08   ` Vikas Rawal
2022-11-13  2:39 ` Jean Louis
2022-11-13 12:05   ` juh [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=Y3DdmQGCSBlU/m3r@odysseus \
    --to=juh+ntg-context@mailbox.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=juh@mailbox.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).