[ 
https://issues.apache.org/jira/browse/CASSANDRA-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis resolved CASSANDRA-2876.
---------------------------------------

    Resolution: Fixed
      Assignee: Rick Shaw

Resolving as fixed since the subtasks are, but really JDBC driver moved 
out-of-tree anyway.
                
> JDBC 1.1 Roadmap of Enhancements
> --------------------------------
>
>                 Key: CASSANDRA-2876
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2876
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Drivers
>    Affects Versions: 0.8.1
>            Reporter: Rick Shaw
>            Assignee: Rick Shaw
>            Priority: Minor
>              Labels: cql, jdbc
>             Fix For: 1.1
>
>
> Organizational ticket to tie together the proposed improvements to 
> Cassandra's JDBC driver  in order to coincide with the 1.0 release of the 
> server-side product in the fall of 2011.
> The target list of improvements (in no particular order for the moment) are 
> as follows:
> # Complete the {{PreparedStatement}} functionality by implementing true 
> server side variable binding against pre-compiled CQL references.
> # Provide simple {{DataSource}} Support.
> # Provide a full {{PooledDataSource}} implementation that integrates the C* 
> JDBC driver with App Servers, JPA implementations and POJO Frameworks (like 
> Spring).
> # Add the {{BigDecimal}} datatype to the list of {{AbstractType}} classes to 
> complete the planned datatype support for {{PreparedStatement}} and 
> {{ResultSet}}.
> # Enhance the {{Driver}} features to support automatic error recovery and 
> reconnection.
> # Support {{RowId}} in {{ResultSet}}
> # Allow bi-directional row access scrolling  to complete functionality in the 
> {{ResultSet}}.
> # Deliver unit tests for each of the major components of the suite.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to