<!-- 
RSS generated by JIRA (4.4#649-r158309) at Wed May 22 23:03:58 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://dev.clojure.org/jira/si/jira.issueviews:issue-xml/JDBC-6/JDBC-6.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Clojure JIRA</title>
    <link>http://dev.clojure.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>4.4</version>
        <build-number>649</build-number>
        <build-date>25-07-2011</build-date>
    </build-info>

<item>
            <title>[JDBC-6] Add hook to allow operations on PreparedStatement prior to query execution</title>
                <link>http://dev.clojure.org/jira/browse/JDBC-6</link>
                <project id="10021" key="JDBC">java.jdbc</project>
                        <description>&lt;p&gt;It would be very useful to be able to pass in a function argument to several c.j.j functions that would be called on the PreparedStatement before executing the query, for example, calling setFetchSize(). I&apos;m not sure what the syntax should look like for this...&lt;/p&gt;</description>
                <environment></environment>
            <key id="14443">JDBC-6</key>
            <summary>Add hook to allow operations on PreparedStatement prior to query execution</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</type>
                                <priority id="3" iconUrl="http://dev.clojure.org/jira/images/icons/priority_major.gif">Major</priority>
                    <status id="5" iconUrl="http://dev.clojure.org/jira/images/icons/status_resolved.gif">Resolved</status>
                    <resolution id="1">Completed</resolution>
                                <assignee username="seancorfield">Sean Corfield</assignee>
                                <reporter username="seancorfield">Sean Corfield</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 May 2011 20:06:23 -0500</created>
                <updated>Wed, 10 Aug 2011 02:23:49 -0500</updated>
                    <resolved>Wed, 10 Aug 2011 02:23:49 -0500</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="26580" author="seancorfield" created="Sun, 17 Jul 2011 03:36:38 -0500"  >&lt;p&gt;I&apos;ve started the work to reorganize the code to better expose the statement object for this sort of manipulation.&lt;/p&gt;</comment>
                    <comment id="26582" author="seancorfield" created="Sun, 17 Jul 2011 17:57:16 -0500"  >&lt;p&gt;Two options under consideration:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;allow raw PreparedStatement to be passed in by user where appropriate so they have complete control&lt;/li&gt;
	&lt;li&gt;allow map of settings that would be used to create the PreparedStatement and set its options&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I like the latter better but Alan Malloy made the point that the former may still be needed for total control anyway.&lt;/p&gt;

&lt;p&gt;I&apos;m leaning toward adding a function to ease creation of PreparedStatement objects to at least provide a clean API and then I&apos;ll consider how best to integrate that with the other functions.&lt;/p&gt;</comment>
                    <comment id="26583" author="seancorfield" created="Sun, 17 Jul 2011 22:02:17 -0500"  >&lt;p&gt;Added prepare-statement* to jdbc.internal which takes a connection, a SQL string and a map of options; returns a PreparedStatement. Will expose this in top-level.&lt;/p&gt;

&lt;p&gt;with-query-results now allows the first element in the sql-params vector to be either:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;PreparedStatement object created by the user&lt;/li&gt;
	&lt;li&gt;map of options passed to prepare-statement* in order to create the PreparedStatement&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Options supported are in the docstring. May add additional post-creation options (beyond fetch-size and max-rows).&lt;/p&gt;</comment>
                    <comment id="26719" author="seancorfield" created="Wed, 10 Aug 2011 02:23:49 -0500"  >&lt;p&gt;Users have verified that being able to specify :fetch-size in with-query-results handles the common use cases for performance.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>