ClojureQL - 1.0.0 now in beta
bestinclass.dk
ClojureQL - 1.0.0 now in beta
1–10 of 23 posts
Re: ClojureQL - 1.0.0 now in beta
#2I've been looking for something similar to this! Having just learned of Relational Algebra in class I've always wondered why we went with a more difficult to understand abstraction of SQL.
Re: ClojureQL - 1.0.0 now in beta
#3I've been looking for something similar to this! Having just learned of Relational Algebra in class I've always wondered why we went with a more difficult to understand abstraction of SQL.
I wrote my web app DB access in pure SQL and I'm thinking if its worth a rewrite with something like this. Initially I thought I could "abstract" SQL with a few functions of mine, but that was very short-sighted thinking.
Re: ClojureQL - 1.0.0 now in beta
#4I've been waiting for this rewrite! By the looks of this page, you've done a fine job. Excellent work team ClojureQL! I'm looking forward to giving it a test run.
Re: ClojureQL - 1.0.0 now in beta
#5This looks pretty sweet. Can't wait to try it out.
Re: ClojureQL - 1.0.0 now in beta
#6I can not understand what problem this library solves ? Why to write SQL in Clojure and translate it back to SQL ?
Examples on website are quite simplistic. They are far away from real life SQL queries that usually bigger and more complex (not select and join couple of tables). What about "group by", joining 5 or 8 tables etc.? How you are supposed to prototype and test your queries on existing schema (there are many good graphical clients for many RDBMSes)? There are many questions remaining unanswered.
At least Clojre-QL do not try to fit a square peg into round hole like Hibernate. Personally I liked Hibernate for some period, until I sat down and learned to use SQL.
Re: ClojureQL - 1.0.0 now in beta
#7I can not understand what problem this library solves ? Why to write SQL in Clojure and translate it back to SQL ? Examples on website are quite simplistic. They are far away from real life SQL queries that usually bigger and more complex (not select and join couple of tables). What about "group by", joining 5 or 8 tables etc.? How you are supposed to prototype and test your queries on existing schema (there are many…
I suggest you read this post and its comments: http://magicscalingsprinkles.wordpress.com/2010/01/28/why-i-...
Re: ClojureQL - 1.0.0 now in beta
#8I can not understand what problem this library solves ? Why to write SQL in Clojure and translate it back to SQL ? Examples on website are quite simplistic. They are far away from real life SQL queries that usually bigger and more complex (not select and join couple of tables). What about "group by", joining 5 or 8 tables etc.? How you are supposed to prototype and test your queries on existing schema (there are many…
I suggest you read this post and its comments: http://magicscalingsprinkles.wordpress.com/2010/01/28/why-i-...
I read the article. The guy claims that SQL is hard -- yes it is hard for real life cases and there are limitations imposed by underlying theory (relational algebra). Joining the table with itself may be little mind-blowing when you do it first time. It still does not mean that we need to write queries in different language and translate them back to SQL.
A simple question is "how the hell you use prepared statements with such libraries"? And the answer will be is that the FRAMEWORK need to be extended further in order to support them. In other words once you abandon SQL you will never have the same flexibility that it gives, because of artificial constraints imposed by every framework. And your code will become more and more complex because of all these frameworks that are invented not of the real need but as an programming exercise.
Re: ClojureQL - 1.0.0 now in beta
#9Earlier quoted context omitted.
I suggest you read this post and its comments: http://magicscalingsprinkles.wordpress.com/2010/01/28/why-i-...
I read the article. The guy claims that SQL is hard -- yes it is hard for real life cases and there are limitations imposed by underlying theory (relational algebra). Joining the table with itself may be little mind-blowing when you do it first time. It still does not mean that we need to write queries in different language and translate them back to SQL. A simple question is "how the hell you use prepared statements…
I suggest you read this article, http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
Re: ClojureQL - 1.0.0 now in beta
#10I can not understand what problem this library solves ? Why to write SQL in Clojure and translate it back to SQL ? Examples on website are quite simplistic. They are far away from real life SQL queries that usually bigger and more complex (not select and join couple of tables). What about "group by", joining 5 or 8 tables etc.? How you are supposed to prototype and test your queries on existing schema (there are many…
Clojure code is Clojure data. So, these SQL statements are really just nested lists.
Instead of writing an ad-hoc SQL parser and doing string manipulation, you can write relatively simple Clojure functions to manipulate these lists and generate valid SQL.