From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [Babel] How to pass variables to SQL blocks?
Date: Mon, 13 Dec 2010 15:06:37 -0700 [thread overview]
Message-ID: <87mxo9fhua.fsf@gmail.com> (raw)
In-Reply-To: <80fwu1pdsj.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Mon, 13 Dec 2010 22:23:56 +0100")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>>> (I thought this feature would be implemented using "real" SQL vars, hence my @
>>> prefix. But viewing the code shows the replacement is made outside of the SQL
>>> snippet's knowledge.)
>>
>> I agree that using real SQL variables would be preferable. If you want
>> to submit a patch to this effect I would be happy to review it and apply.
>
> I'll give a shot -- not in the really short term, though. Which example should
> I look at? shell?
>
great, and please no rush.
shell actually has rather sophisticated variable passing, maybe sqlite
and gnuplot would provide examples more similar to sql.
>
>
>>> Maybe the following should be put on some TODO list, even if not urgent?
>>>
>>>>> * No warning if block does not exist
>>>>>
>>>>> Please note that inexistent references are ignored, without further
>>>>> notice. That's the case for such a block (where I forgot the number
>>>>> suffix):
>>>>>
>>>>> #+srcname: contains-inexistent-ref
>>>>> #+begin_src sql :noweb yes
>>>>> <<add-column-in-table>>
>>>>> #+end_src
>>
>> The lack of notice (or error) was originally intentional. The logic
>> being that there may be languages in which <<something>> constructs are
>> part of the language syntax, and in those languages Org-mode should
>> ignore such constructs unless the "something" contained in the <<>>'s is
>> actually the name of a code block.
>>
>> It may make sense to revisit this design decision.
>
> IMHO, it should, yes. Because a typo is so easy, and the results can be very
> different then, from what's expected... OK, there is always a preview mode,
> but an alert is better (for me).
>
> Maybe adding an option for those languages, that would suppress such warnings?
>
That may be the best idea, once again a header argument may be the most
flexible solution.
>
> Re helper functions for such named code blocks, do you have an idea what I
> should do to have the IMenu index of code blocks working? See previous thread
> [[http://mid.gmane.org/808w09foxd.fsf%40missioncriticalit.com][Re: imenu
> support for babel blocks]].
>
I don't have any experience with IMenu support, however to map over all
code blocks in a file extracting information I would suggest using the
org-babel-map-src-blocks macro.
Cheers -- Eric
>
> Thanks for any hint!
>
> Best regards,
> Seb
prev parent reply other threads:[~2010-12-13 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 16:07 [Babel] How to pass variables to SQL blocks? Sébastien Vauban
2010-12-01 2:34 ` Eric Schulte
2010-12-01 10:35 ` Sébastien Vauban
2010-12-13 19:53 ` Eric Schulte
2010-12-13 21:23 ` Sébastien Vauban
2010-12-13 22:06 ` Eric Schulte [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:
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=87mxo9fhua.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).