You can wrap your code in (entities ...) and/or (identifiers ...) and
it will apply to all the java.jdbc calls inside.
Clojure/core have specifically said they don't want *dynamic-vars* in
contrib libraries.
We have thousands of lines of java.jdbc code at work and name mapping
hasn't been an issu
Then, how about making them global so that they can be altered?
I know global parameters are ugly, but having to specify them every time is
really a pain.
On Tuesday, August 27, 2013 2:32:20 AM UTC+9, Sean Corfield wrote:
>
> The db-spec is not used by the DSL. Name mapping is a function of the
The db-spec is not used by the DSL. Name mapping is a function of the
DSL, in general. This request has come up in the past and it just
isn't practical since the db-spec is completely independent of the
DSL.
On Mon, Aug 26, 2013 at 6:06 AM, Alice wrote:
> It would be convenient if I can specify t
Yes. It's described at
http://clojure-doc.org/articles/ecosystem/java_jdbc/name_mapping.html.
On Monday, August 26, 2013 10:13:22 PM UTC+9, Shantanu Kumar wrote:
>
> Hi Alice,
>
> Do you mean default `values` for entity columns for INSERT statements? And
> by `identifiers function` did you mean
Hi Alice,
Do you mean default `values` for entity columns for INSERT statements? And
by `identifiers function` did you mean functions that decorate an
identifier representation in an SQL statement -- for example, column name
emp_id could become `emp_id` on MySQL?
Shantanu
On Monday, 26 August
