http://dev.clojure.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JDBC+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC An XML representation of a search request en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/JDBC-55 java.jdbc <p>Reflection warning, clojure/java/jdbc.clj:618:50 - reference to field executeQuery can't be resolved.<br/> Reflection warning, clojure/java/jdbc.clj:618:33 - reference to field close can't be resolved.</p> JDBC-55

More reflection warnings to investigate

Task Major Resolved Completed Sean Corfield Sean Corfield Tue, 14 May 2013 20:04:54 -0500 Tue, 21 May 2013 10:08:02 -0500 Tue, 21 May 2013 10:08:02 -0500 0 0 <p>Patch jdbc-55-fix-reflection-warnings-v1.txt dated May 15 2013 adds one more type hint that eliminates the two mentioned instances of reflection.</p> <p>Patch applied. Thank you!</p> Global Rank http://dev.clojure.org/jira/browse/JDBC-57 java.jdbc <p>This is just a suggestion, and i am not sure if it is the right way to do this. </p> <p>When fetching data from Oracle the oracle jdbc driver returns all the numeric type columns as BigDecimal and date/datetime columns as oracle.sql.TIMESTAMP. This causes a lot of headache as we have to remember to convert the data to the correct type. </p> <p>Although, this can be handled at the application level by using a :row-fn, it would be really nice if this library handles the conversion itself.</p> Oracle 10g and above JDBC-57

Better support for Oracle

Enhancement Major Resolved Completed Sean Corfield Manish Handa Sat, 18 May 2013 13:49:57 -0500 Mon, 20 May 2013 22:52:57 -0500 Mon, 20 May 2013 22:52:57 -0500 0 0 <p>Patch for handling results returned by oracle jdbc thin driver</p> <p>I think the right solution here will be to modify the result-set-read-column protocol function to be passed rsmeta and i and then Oracle users can extend the protocol to those types and perform the conversions they want. I don't believe automcatically converting BigDecimal is going to be the right choice for all users although doing the conversion for oracle.sql.TIMESTAMP is a more arguable conversion.</p> <p>Agreed. I thought of this, but it requires changing the protocol to take rsmeta along with the column index. i have uploaded another patch for this change.</p> <p>Also, it'll be better to leave the handling of oracle.sql.Timestamp to the application as it needs a dependency on the oracle thin driver (which we should certainly not add to java.jdbc). </p> <p>So, after this updated protocol, the oracle users can extend it with something like this (much better now):</p> <p>;;; Oracle users can define this in their applications<br/> ;; to extend it to BigDecimal and other oracle types<br/> (extend-protocol IResultSetReadColumn<br/> oracle.sql.TIMESTAMP<br/> (result-set-read-column <span class="error">&#91;x _ _&#93;</span> (.timestampValue x))</p> <p> java.math.BigDecimal<br/> (result-set-read-column <span class="error">&#91;val rsmeta idx&#93;</span><br/> (if-not (= (.getScale rsmeta idx) 0)<br/> (.doubleValue val) ;;; reals<br/> (if (= (.getPrecision rsmeta idx) 1)<br/> (= 1 (.longValue val)) ;;; booleans<br/> (.longValue val))))) ;; integrals</p> <p>Thanx. Yes, that was where I was going with this, and while we're in alpha for 0.3.0 I'm not averse to changing the signatures of new stuff introduced in the API rewrite. I'll review the patch later and probably roll it in this week (I just got back from a web tech conference in MN and I'm busy catching up on work!).</p> <p>Patch applied. Tests updated to match<img class="emoticon" src="http://dev.clojure.org/jira/images/icons/emoticons/warning.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>. Will be in 0.3.0-alpha5.</p> Global Rank