[ANN] HugSQL 0.4.0 release

2016-02-15 Thread Curtis Summers
of partial SQL statements when constructing complex SQL queries. - has protocol-based adapters supporting multiple database libraries and ships with adapters for clojure.java.jdbc (default) and clojure.jdbc Thanks! Curtis Summers -- You received this message because you are subscrib

Re: [ANN] 0.3.0 HugSQL release

2015-11-12 Thread Curtis Summers
Colin, I've added an issue to explore composable features for a future HugSQL release: https://github.com/layerware/hugsql/issues/12 All ideas welcome! Thanks! On Wed, Nov 11, 2015 at 11:40 PM, Robin Heggelund Hansen < skinney...@gmail.com> wrote: > Fantastic release Curtis. This is an awesom

Re: [ANN] 0.3.0 HugSQL release

2015-11-11 Thread Curtis Summers
as that comment in the page bought > the two into comparison. > > Thanks, and again, congratulations! > > On 12 Nov 2015, at 00:51, Curtis Summers > wrote: > > I'm happy to announce the 0.3.0 release of HugSQL. > > HugSQL is a Clojure library for embra

[ANN] 0.3.0 HugSQL release

2015-11-11 Thread Curtis Summers
bc (default) and clojure.jdbc Thanks! Curtis Summers -- 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

Re: [ANN] a HugSQL adapter for postgres.async

2015-11-04 Thread Curtis Summers
Author of HugSQL here. Yes, I'm working on a new docs site for HugSQL since the README is getting a bit long, and it will have a Yesql comparison as Robin stated. I think Robin's list if fairly accurate. I may approach it from the design goals point-of-view along with usage differences in t

[ANN] HugSQL 0.1.1 - Embrace SQL

2015-10-21 Thread Curtis Summers
dges, your particular use cases, etc. See the README for clojar install information: https://github.com/layerware/hugsql Thanks, Curtis Summers -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to cloj

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2301, Transducers!

2014-08-09 Thread Curtis Summers
The issue is resolved for me also. Thanks! --Curtis On Sat, Aug 9, 2014 at 10:18 AM, Paul Burt wrote: > On Saturday, 9 August 2014 16:03:57 UTC+1, Rick B wrote: > > There was a cache issue for the maven-metadata.xml and the possibly the > jar files for 0.0-2301 and 0.0-2307. We have purged o

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2301, Transducers!

2014-08-09 Thread Curtis Summers
I think this may be a cache issue with the central repo. I can both see the file via browsing and they are in the index for me, but the actual jar file brings up a 404: http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/clojurescript-0.0-2307.jar However, appending a junk query s

Re: Leiningen profile problem

2014-07-28 Thread Curtis Summers
Paul, Leiningen can isolate the target-paths by profile if you use :target-path in your project.clj with the %s in it. Per the sample project.clj file ( https://github.com/technomancy/leiningen/blob/master/sample.project.clj): ;; All generated files will be placed in :target-path. In order

Re: reloading enlive templates

2014-07-03 Thread Curtis Summers
I'm using ring.middleware.force-reload to always reload the namespaces that reference my enlive templates. (only in dev, of course) https://github.com/citizenparker/ring-middleware-force-reload Hope that helps, Curtis On Wednesday, July 2, 2014 3:14:16 PM UTC-5, Sven Richter wrote: > > Hi, >

Re: evaluation order in loading file/project (with leiningen)

2013-09-03 Thread Curtis Summers
If you're defining functions depending on yet-to-be-defined functions, you may need to use the "declare" macro. So, you may need to loop through your data with declare first, and then proceed with the definitions. http://clojure.github.io/clojure/clojure.core-api.html#clojure.core/declare Curt

Re: [Proposal] Simplified 'ns' declaration

2013-08-06 Thread Curtis Summers
I agree that wildcards make it "easy" (in the nearness sense), but from a long-term maintainability standpoint, I'd prefer to have explicit imports as is. When I'm reading your code a year from now and need to look-up the docs on a class, wildcards make me (and anyone else in the future) have t