Re: clojure.java.jdbc 0.0.1 released

2011-05-09 Thread Armando Blancas
Cool. I look forward to having approved 1.0.0 releases of contrib libraries. On May 9, 3:28 pm, Sean Corfield wrote: > On Mon, May 9, 2011 at 2:38 PM, Armando Blancas > > wrote: > > Having no clue what to make of 0.0.1 precisely w.r.t. its previous > > versions numbers, I gathered it's because y

Re: clojure.java.jdbc 0.0.1 released

2011-05-09 Thread Sean Corfield
On Mon, May 9, 2011 at 2:38 PM, Armando Blancas wrote: > Having no clue what to make of 0.0.1 precisely w.r.t. its previous > versions numbers, I gathered it's because you can't make out anybody's > modules anyway, in which I agree. Well, the previous modules didn't really have version numbers in

Re: clojure.java.jdbc 0.0.1 released

2011-05-09 Thread Armando Blancas
Having no clue what to make of 0.0.1 precisely w.r.t. its previous versions numbers, I gathered it's because you can't make out anybody's modules anyway, in which I agree. On May 9, 11:34 am, Sean Corfield wrote: > On Mon, May 9, 2011 at 8:22 AM, Armando Blancas > > wrote: > > Yeap. Release numb

Re: clojure.java.jdbc 0.0.1 released

2011-05-09 Thread Sean Corfield
On Mon, May 9, 2011 at 8:22 AM, Armando Blancas wrote: > Yeap. Release numbers have become meaningless; your point is well > taken. Not sure what you mean by that? The "new contrib" libraries can be seen here, with their current, evolving version numbers: https://oss.sonatype.org/index.html#nex

Re: clojure.java.jdbc 0.0.1 released

2011-05-09 Thread Armando Blancas
Yeap. Release numbers have become meaningless; your point is well taken. On May 8, 7:11 pm, Sean Corfield wrote: > The library formerly known as clojure.contrib.sql has had it's first > non-snapshot release. > > Features added: > * returns generated keys for single record inserts > * supports nam

clojure.java.jdbc 0.0.1 released

2011-05-08 Thread Sean Corfield
The library formerly known as clojure.contrib.sql has had it's first non-snapshot release. Features added: * returns generated keys for single record inserts * supports naming strategies to allow to override the conversion of keywords to/from SQL entity names * exposes resultset-seq that respect