[jira] [Created] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
BeanProcessor method processColumn should take SQLXML in consideration
----------------------------------------------------------------------

                 Key: DBUTILS-84
                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
             Project: Commons DbUtils
          Issue Type: Improvement
    Affects Versions: 1.4
         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
            Reporter: Tiago Cavaleiro
            Priority: Minor




I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.

Part of the problem is related with the fact the SQL Server driver returns a String.
The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.


The correction I've made on the DbUtils was to add the following code:

{code:title=BeanProcess.java|borderStyle=solid}
    protected Object processColumn(ResultSet rs, int index, Class<?> propType)
        throws SQLException {

        (...)
       
        } else if (propType.equals(SQLXML.class)) {
        return rs.getSQLXML(index);
           
        } else {
            return rs.getObject(index);
        }
{code}




--
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 | Threaded
Open this post in threaded view
|

[jira] [Updated] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)

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

Tiago Cavaleiro updated DBUTILS-84:
-----------------------------------

    Attachment: BeanProcessor.java

BeanProcess with patch
               

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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 | Threaded
Open this post in threaded view
|

[jira] [Updated] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
In reply to this post by Richard (Jira)

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

William R. Speirs updated DBUTILS-84:
-------------------------------------

      Description:

I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.

Part of the problem is related with the fact the SQL Server driver returns a String.
The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.


The correction I've made on the DbUtils was to add the following code:

{code:title=BeanProcess.java|borderStyle=solid}
    protected Object processColumn(ResultSet rs, int index, Class<?> propType)
        throws SQLException {

        (...)
       
        } else if (propType.equals(SQLXML.class)) {
        return rs.getSQLXML(index);
           
        } else {
            return rs.getObject(index);
        }
{code}




  was:


I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.

Part of the problem is related with the fact the SQL Server driver returns a String.
The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.


The correction I've made on the DbUtils was to add the following code:

{code:title=BeanProcess.java|borderStyle=solid}
    protected Object processColumn(ResultSet rs, int index, Class<?> propType)
        throws SQLException {

        (...)
       
        } else if (propType.equals(SQLXML.class)) {
        return rs.getSQLXML(index);
           
        } else {
            return rs.getObject(index);
        }
{code}




    Fix Version/s: 1.5
   

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>             Fix For: 1.5
>
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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 | Threaded
Open this post in threaded view
|

[jira] [Commented] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
In reply to this post by Richard (Jira)

    [ https://issues.apache.org/jira/browse/DBUTILS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157592#comment-13157592 ]

William R. Speirs commented on DBUTILS-84:
------------------------------------------

Applied in r1206562
               

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>             Fix For: 1.5
>
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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 | Threaded
Open this post in threaded view
|

[jira] [Commented] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
In reply to this post by Richard (Jira)

    [ https://issues.apache.org/jira/browse/DBUTILS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408088#comment-13408088 ]

Stevo Slavic commented on DBUTILS-84:
-------------------------------------

Since [change has been applied|http://svn.apache.org/viewvc?view=revision&revision=1206562], why not mark the issue as implemented?
               

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>             Fix For: 1.5
>
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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 | Threaded
Open this post in threaded view
|

[jira] [Resolved] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
In reply to this post by Richard (Jira)

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

Simone Tripodi resolved DBUTILS-84.
-----------------------------------

    Resolution: Fixed
      Assignee: William R. Speirs

yeah, issue marked as resolved due to patch appliance at r r1206562
               

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Assignee: William R. Speirs
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>             Fix For: 1.5
>
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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 | Threaded
Open this post in threaded view
|

[jira] [Closed] (DBUTILS-84) BeanProcessor method processColumn should take SQLXML in consideration

Richard (Jira)
In reply to this post by Richard (Jira)

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

Simone Tripodi closed DBUTILS-84.
---------------------------------


1.5-RC released
               

> BeanProcessor method processColumn should take SQLXML in consideration
> ----------------------------------------------------------------------
>
>                 Key: DBUTILS-84
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-84
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: Windows 7 + IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20110216_75791 (JIT enabled, AOT enabled)
>            Reporter: Tiago Cavaleiro
>            Assignee: William R. Speirs
>            Priority: Minor
>              Labels: SQLXML, sqlserver
>             Fix For: 1.5
>
>         Attachments: BeanProcessor.java
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I was experimenting DbUtils and discovered that if the result set contains a SQLXML column using the BeanProcessor the returned type will be a String and not a java.sql.SQLXML.
> Part of the problem is related with the fact the SQL Server driver returns a String.
> The call to ResultSet.getObject([SQLXML index]) is returning a String instead of the java.sql.SQLXML, but if we call the ResultSet.getSQLXML([SQLXML index]) it works as expected.
> The correction I've made on the DbUtils was to add the following code:
> {code:title=BeanProcess.java|borderStyle=solid}
>     protected Object processColumn(ResultSet rs, int index, Class<?> propType)
>         throws SQLException {
>         (...)
>        
>         } else if (propType.equals(SQLXML.class)) {
>         return rs.getSQLXML(index);
>            
>         } else {
>             return rs.getObject(index);
>         }
> {code}

--
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