[Clojure] ANN: clojure.java.jdbc 0.0.7

On Oct 12, 5:37 am, Sean Corfield wrote:
Changes in 0.0.7:

* Fix JDBC-9 by renaming duplicate columns instead of throwing an exception.
- thanx to Peter Siewert!
* Fix JDBC-16 by ensuring do-prepared works with no param-groups provided.
* Fix JDBC-17 by adding type hints to remove more reflection warnings.
- thanx to Stuart Sierra!
Documentation:
* Address JDBC-4 by documenting how to do connection pooling.

Plans:

Once JDBC-3 / JDBC-15 have been addressed (use of deprecated
struct-map stuff), I'll declare 0.1.0 and ask Clojure/core what would
be needed for a 1.0.0 release. Feel free to provide feedback for
future development here:

http://dev.clojure.org/display/design/java.jdbc

Earlier changes...

Changes in 0.0.6:

* Move former tests to test-utilities namespace - these do not touch a database
* Convert old "test" examples into real tests against real databases
- tested locally against MySQL, Apache Derby, HSQLDB
- build system should run against Apache Derby, HSQLSB
- will add additional databases later
* Fix JDBC-12 by removing batch when doing a single update
* Remove wrapping of exceptions in transactions to make it easier to
work with SQLExceptions

Changes in 0.0.5:

* Add prepare-statement function to ease creation of PreparedStatement
with common options:
- see docstring for details
* with-query-results now allows the SQL/params vector to be:
- a PreparedStatement object, followed by any parameters the SQL needs
- a SQL query string, followed by any parameters it needs
- options (for prepareStatement), a SQL query string, followed by
any parameters it needs
* Add support for databases that cannot return generated keys (e.g., HSQLDB)
- insert operations silently return the insert counts instead of
generated keys
- it is the user's responsibility to handle this if you're using
such a database!

Changes in 0.0.4:

* Fix JDBC-2 by allowing :table-spec {string} at the end of
create-table arguments:
(sql/create-table :foo [:col1 "int"] ["col2" :int] :table-spec
"ENGINE=MyISAM")
* Fix JDBC-8 by removing all reflection warnings
* Fix JDBC-11 by no longer committing the transaction when an Error occurs
* Clean up as-... functions to reduce use of (binding)
* Refactor do-prepared*, separating out return keys logic and
parameter setting logic
- in preparation for exposing more hooks in PreparedStatement
creation / manipulation

Changes in 0.0.3:

* Fix JDBC-10 by using .executeUpdate when generating keys (MS SQL
Server, PostgreSQL compatibility issue)

Changes in 0.0.2:

* Fix JDBC-7 Clojure 1.2 compatibility (thanx to Aaron Bedra!)

Changes in 0.0.1 (compared to clojure.contrib.sql):

* Exposed print-... functions for exception printing; no longer writes
exceptions to *out*
* Add clojure.java.jdbc/resultset-seq (to replace
clojure.core/resultset-seq which should be deprecated)
* Add support for naming and quoting strategies - seehttp://clojure.github.com/java.jdbc/doc/clojure/java/jdbc/NameMapping...
- The formatting is a bit borked, Tom F knows about this and is
working on an enhancement to auto-doc to improve it
* Add ability to return generated keys from single insert operations,
add insert-record function
* Clojure 1.3 compatibility
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View --http://corfield.org/
World Singles, LLC. --http://worldsingles.com/
Railo Technologies, Inc. --http://www.getrailo.com/

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

On Tue, Oct 11, 2011 at 6:58 PM, jaime wrote:
will the 1.0.0 be included in core or contrib package?

On Wed, Oct 12, 2011 at 1:42 AM, keeds wrote:
I'm having problems with MS Access ODBC driver with JDBC ODBC bridge and
parameterised statements.

On Thu, Oct 13, 2011 at 1:35 AM, Marko Kocić wrote:
Looking at the log seems like MS Access doesn't support prepared statements.

On Mon, Nov 7, 2011 at 3:04 PM, keeds wrote:
Some more (blind) delving shows that the only difference between the
versions is that clojure1.2 and contrib pass the 14 value as a
java.lang.Integer whereas clojure1.3 and java.jdbc pass the value 14 as a
java.lang.Long and this is what blows the .setObject call.
Strings work fine as does forcing 14 to be an Integer by passing it as
(Integer. 14)