Hi Sean & Matching Socks,
first off, I like the new API design. Here are my questions and
suggestions:
1.) Despite the asymmetry I'm also thinking that passing entities
and identifiers functions via the "db" argument is quite
convienient. Otherwise I always have to wrestle with those extra
parameters and pass them through my underlying SQL generation
functions. Which I have to to with the db anyway (maybe one level
less).
2.) The default naming strategy for columns coming from the
database is at the moment "lower-case". Wouldn't it be more
idiomatic to lower case and replace "_" with "-". That would be
more consistent with the Clojure defaults of naming keywords at
the expense of maybe performance. I use this naming strategy for
example, because I don't want to constantly remember which keys
in my maps use the Clojure and which the database "convention".
Would this be an option for 0.3.0?
3.) Would it make sense to define some connection spec, into
which the current specs get translated to? Something like the
Ring SPEC for connections. I'm often interested in the name of
the database, the credentials of the hostname the database is
running on, etc. Something like this?
{:product :postgresql
:server-name "example.com"
:server-port 5432
:username "tiger"
:password "scotch"
:db "my_db"
}
Othwerwise thanks for your work on clojure.java.jdbc,
Roman.
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
