> > given java.jdbc's position as the sort of lower level glue all these > libraries are built on, maybe better then including a DSL in java.jdbc > would be including an AST (some data representation of sql) and a > compiler for same. >
Yeah, that's exactly what I wanted to suggest too. Seems like all would benefit from that. Though, the same idea has already been discussed on the list some time ago. @Sean Corfield: > jsql has completely different goals to ClojureQL/Korma and is mostly a > convenience for generating the sort of SQL that the update!, insert! > and delete! methods need under the hood (c.j.jdbc has to generate that > SQL anyway - might as well make the methods public). The > select/where/order-by has evolved out of our common usage at World > Singles where we have get-by-id and find-by-keys and similar CRUD > functions. jsql is deliberately very close to the "metal" of SQL and > is not intended to be composable etc. Folks wanting a full-blown DSL > should indeed use Korma (or ClojureQL). Ok, I see. I've misunderstood the goals. Though, it still duplicates significant part of clojureql\korma, right? What do you think about AST\compiler thing? -- 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
