db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-856) modify setCharacterStreamInternal to take a long for the length, and perform the > max int check in the method
Date Thu, 26 Jan 2006 00:32:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-856?page=comments#action_12364041 ] 

David Van Couvering commented on DERBY-856:
-------------------------------------------

I could have sworn Dan commented on this, but I can't find his email, so I'll say it: I think
the code should use StandardException.newException() rather than Util.newEmbedSQLException.
 This seems especially important as we look forward to JDBC4 support, as the recent thread
with Anurag exemplifies...

So, something like

Util.generateCsSQLException(StandardException.newException(SQLState.LANG_INVALID_COLUMN_LENGTH,
"setCharacterStreamInternal"));

seems more standard

David

> modify setCharacterStreamInternal to take a long for the length, and perform the >
max int check in the method
> --------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-856
>          URL: http://issues.apache.org/jira/browse/DERBY-856
>      Project: Derby
>         Type: Improvement
>   Components: JDBC
>     Versions: 10.2.0.0
>  Environment: All Environments
>     Reporter: V.Narayanan
>     Assignee: V.Narayanan
>     Priority: Minor
>  Attachments: setCharacterStreamInternal.diff, setCharacterStreamInternal.stat
>
> A similar change to setBinaryStreamInternal is being handled as part of DERBY-599. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message