SQLRat 0.2 is released to Clojars. Highlights of the release: - DSL for SQL clauses, Sub-query support - Support for :groupby and :other attributes in entity/find-xxx functions - Support large sized query result-sets (with-query-results style) - *assert-args* flag for development mode (can be turned off in production)
http://bitbucket.org/kumarshantanu/sqlrat/src This version makes SQLRat usable for ETL/Data-warehousing jobs due to the large result-sets support and the clause API will likely make querying easier. The clause API is not complete; it needs to further evolve. There is plenty of work ahead (listed in CHANGES file) and feedback/contribution is most welcome. Regards, Shantanu On Oct 6, 2:27 pm, Shantanu Kumar <kumar.shant...@gmail.com> wrote: > On Oct 6, 8:39 am, nchubrich <nchubr...@gmail.com> wrote: > > > > So, the question is -- isSQLRatdoing more or less the same thing as > > > ClojureQL? Partly "yes", but mostly "no". > > > Thanks Shantanu! So I suppose one way you could use them both is > > simply use the SQL compilation feature of ClojureQL----you could pass > >SQLRata raw SQL query created from ClojureQL? > > If you look at the Entity[1] API and the CHANGES[2] file you will > noticeSQLRatneeds to work with the entity/table meta data and > relation meta data.SQLRataccepts the WHERE, GROUP-BY and OTHER > clauses in the find-xxx functions where you can pass pre-generated SQL > clauses. Whether such partial SQL clauses can be generated using > ClojureQL is something I am not sure of. > > ClojureQL provides database-agnostic API for > (a) creating tables (also for altering tables?) and > (b) reporting queries involving JOIN/UNION etc > > These are not provided bySQLRat. I think you can readily use them > while working in mixed-mode (ClojureQL andSQLRat). > > [1]http://bitbucket.org/kumarshantanu/sqlrat/src/tip/src/main/clj/org/bi... > [2]http://bitbucket.org/kumarshantanu/sqlrat/src/tip/CHANGES > > > > > I've used ClojureQL quite a bit, but I haven't attempted to verify its > > database agnoticity. I think having that is a good goal, though. I'd > > be curious to hear what the ClojureQL developers think of working with > > your project. > > IMHO database agnosticism is a good goal indeed -- quite useful for > those having to switch between databases. > > Regards, > Shantanu -- 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
