Daniel Jomphe <danieljom...@gmail.com> writes: > Since Korma appeared, it seems ClojureQL isn't mentioned anywhere anymore. > > Are there solid reasons why Korma took all the attention to itself? Are there > situations in which ClojureQL would be more recommended than Korma?
The functional apporach CQL takes to constructing SQL queries is just right in my book. I want the full power of SQL: unions, intersections, projections, aggregates, functions, composition of qualifiers etc... In my case I've got a database with 100+ tables. A very small set of them are "objects" like users, and organizations. The rest are mostly core.logic fact statements (with type and other metadata) dumped into a table for each relation. Lastly, there are some some index tables to make some common, yet complicated, searches we support really fast. There are almost no artificial keys in the data tables, no notion of object identity for the most part either. We have these soft "entities" which conventiently map into sql data types, so work as key values themselves. I don't wanna diss on Korma tho, just that the data model it is aiming at is not the one I want. -- Craig Brozefsky <cr...@red-bean.com> Premature reification is the root of all evil -- 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
