On Apr 26, 10:13 am, Sean Corfield <seancorfi...@gmail.com> wrote: > On Tue, Apr 26, 2011 at 6:19 AM, David Powell <djpow...@djpowell.net> wrote: > > There is justification for resultset-seq's current behaviour, even if it > > isn't to everyone's preference. > > Agreed. And I would actually want the lowercasing behavior to remain > the default, for my own use anyway. What irks me more is the lack of > translation between foo_bar and :foo-bar or, for folks who camelCase > column names, between fooBar and :foo-bar perhaps. This all goes back > to the idea of a "naming strategy" for translating between Clojure > keywords and SQL entity names. > > I think at this point it makes sense to add a function to c.j.j that > mimics the current resultset-seq functionality but allows for the > application of naming strategies - with the default being the current > behavior, and some other standard strategies available. > > The question then is whether the c.j.j function should also be called > resultset-seq or whether a new name should be picked? > > However, c.j.j functions yield the _result_ of resultset-seq so > perhaps it doesn't even need to expose the function itself? On the > other hand, if c.j.j supports naming strategies to provide different > keyword/entity translations, users may want to be able to apply the > same translations to any raw resultSet objects they have... Thoughts? >
I'd like to at least have the option of passing SQL query strings verbatim to the SQL server and getting returned data verbatim as well, with no auto-quoting or column name munging at all (including downcasing). Name-munging can be implemented on top of functions that return data and column names verbatim, but the opposite is not true. --Brian -- 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
