Re: [ANN] clojure.java.jdbc 0.3.0-beta2 BREAKING CHANGES!

2013-11-25 Thread Sean Corfield
The auto-generated documentation has been updated (thank you Tom!):

http://clojure.github.io/java.jdbc/

This separates the documentation clearly into new API and deprecated
API. Feedback on docstrings in the new API appreciated (via
s...@corfield.org or issues on JIRA if you feel inclined to provide
patches as well).

Sean

On Sun, Nov 24, 2013 at 10:39 PM, Sean Corfield seancorfi...@gmail.com wrote:
 Based on feedback from the community, I have released
 clojure.java.jdbc 0.3.0-beta2 to Maven Central.

 This includes two very important changes:

 * The clojure.java.jdbc.sql and clojure.java.jdbc.ddl namespaces have
 been removed.
 * The API functions that were already marked as deprecated have moved
 to the clojure.java.jdbc.deprecated namespace

 This means that if you depend on the clojure.java.jdbc.sql or
 clojure.java.jdbc.ddl namespaces, which were introduced in
 0.3.0-alpha1, you will need to switch to the java-jdbc/dsl project
 (release 0.1.0 is on Clojars). The new namespaces in that project are
 java-jdbc.sql and java-jdbc.ddl. If you depend on these namespaces, I
 strongly recommend you migrate to a more sophisticated DSL, such as:

 * HoneySQL - https://github.com/jkk/honeysql
 * SQLingvo - https://github.com/r0man/sqlingvo
 * Korma - http://www.sqlkorma.com

 More importantly, if you depend on the older (0.2.3) API in
 clojure.java.jdbc, you'll need to switch to the
 clojure.java.jdbc.deprecated namespace in your code, until you can
 migrate to new API in clojure.java.jdbc instead.

 These steps are more radical than I would have liked but they simplify
 the library and streamline the API - and the auto-generated
 documentation - which should reduce all the confusion expressed about
 the library right now. This will allow the library to move forward in
 a more focused manner, with an API that no longer depends on dynamic
 variables.
 --
 Sean A Corfield -- (904) 302-SEAN
 An Architect's View -- http://corfield.org/
 World Singles, LLC. -- http://worldsingles.com/

 Perfection is the enemy of the good.
 -- Gustave Flaubert, French realist novelist (1821-1880)



-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

Perfection is the enemy of the good.
-- Gustave Flaubert, French realist novelist (1821-1880)

-- 
-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[ANN] clojure.java.jdbc 0.3.0-beta2 BREAKING CHANGES!

2013-11-24 Thread Sean Corfield
Based on feedback from the community, I have released
clojure.java.jdbc 0.3.0-beta2 to Maven Central.

This includes two very important changes:

* The clojure.java.jdbc.sql and clojure.java.jdbc.ddl namespaces have
been removed.
* The API functions that were already marked as deprecated have moved
to the clojure.java.jdbc.deprecated namespace

This means that if you depend on the clojure.java.jdbc.sql or
clojure.java.jdbc.ddl namespaces, which were introduced in
0.3.0-alpha1, you will need to switch to the java-jdbc/dsl project
(release 0.1.0 is on Clojars). The new namespaces in that project are
java-jdbc.sql and java-jdbc.ddl. If you depend on these namespaces, I
strongly recommend you migrate to a more sophisticated DSL, such as:

* HoneySQL - https://github.com/jkk/honeysql
* SQLingvo - https://github.com/r0man/sqlingvo
* Korma - http://www.sqlkorma.com

More importantly, if you depend on the older (0.2.3) API in
clojure.java.jdbc, you'll need to switch to the
clojure.java.jdbc.deprecated namespace in your code, until you can
migrate to new API in clojure.java.jdbc instead.

These steps are more radical than I would have liked but they simplify
the library and streamline the API - and the auto-generated
documentation - which should reduce all the confusion expressed about
the library right now. This will allow the library to move forward in
a more focused manner, with an API that no longer depends on dynamic
variables.
-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

Perfection is the enemy of the good.
-- Gustave Flaubert, French realist novelist (1821-1880)

-- 
-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
Clojure group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.