Re: [O] [babel] Some variables with no default value don't provoke an error

[Eric Schulte]

"Sebastien Vauban" <address@hidden> writes:

> Hi Eric,
>
> As said previously, I've been forced to add a default value to many code
> blocks I had in my local LOB, which I ingest in my `.emacs' file:
>
> #+begin_src emacs-lisp
>  (when (try-require 'ob-lob)
>    (org-babel-lob-ingest "~/emacs/site-lisp/my-local-lob.org"))
> #+end_src
>
> Weirdly enough, in the following code block, I must add a default value for
> vars `table', `column' and `type' but not for the var `nullability'.
>
> I've even been able to add fake vars `something' and `else' with no error
> being reported (at ingestion time):
>
> #+srcname: add-column-in-table(table="", column="", something, type="", else, 
> nullability)
> #+begin_src sql
> -- add column `$column' (if column does not exist yet)
> IF NOT EXISTS (SELECT *
>                FROM INFORMATION_SCHEMA.COLUMNS
>                WHERE TABLE_NAME = '$table'
>                AND COLUMN_NAME = '$column')
> BEGIN
>     ALTER TABLE $table
>     ADD $column $type $nullability
> END
> #+end_src
>
> Note that, in the above state, the code block is ingested with no error, but,
> if I remove the default value of var `table', it then generates back an
> error...
>

I've just pushed up a check for these functional-syntax variables which
will ensure that each is given a default value.  Since this check takes
place at the location of the code block it /does/ include the name of
the code block in the error message.

Cheers -- Eric

>
> Best regards,
>   Seb

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/