[jira] Reopened: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode
[ http://issues.apache.org/jira/browse/DERBY-1500?page=all ] Lance Andersen reopened DERBY-1500: --- This behavior is expected to work correctly in JDBC. The JDB C 4.0 spec has clarified this, ,but it is expected that it would work with any JDBC release. PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode Key: DERBY-1500 URL: http://issues.apache.org/jira/browse/DERBY-1500 Project: Derby Issue Type: Bug Components: JDBC Affects Versions: 10.1.1.0, 10.1.3.1 Environment: WindowsXP Reporter: Markus Fuchs Attachments: ShortTest.java When trying to insert a row into the table SHORT_TEST( ID int, SHORT_VAL smallint) an exception is thrown, if the object value given to PreparedStatement#setObject(int parameterIndex, Object x) is of type Short. The exception thrown is: --- SQLException --- SQLState: 22005 Message: An attempt was made to get a data value of type 'SMALLINT' from a data value of type 'java.lang.Short'. ErrorCode: 2 SQL Exception: An attempt was made to get a data value of type 'SMALLINT' from a data value of type 'java.lang.Short'. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.dataTypeConversion(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setObject(Unknown Source) Tested on Derby 10.1.1.0 and 10.1.3.1. The same test runs fine in network mode. -- 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
[jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12359043 ] Lance Andersen commented on DERBY-253: -- If you are not going to implement this feature, it should throw a SQLException per section 6.2 of the JDBC 3.0 spec (same requirement in JDBC 4 though we are considering adding a new non-transient SQLException as there appears to be a SQLState that we can use... this is under discussion) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream -- Key: DERBY-253 URL: http://issues.apache.org/jira/browse/DERBY-253 Project: Derby Type: Bug Components: Network Client Versions: 10.1.1.0 Reporter: Kathey Marsden Assignee: Olav Sandstaa Priority: Minor setUnicodeStream and getUnicodeStream are deprecated API's Network client PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream() should throw not implemented exceptions rather than trying to handle these calls. Note: The current client implementation of setUnicodeStream() and getUnicodeStream() are broken and can cause unexpected errors -- 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
[jira] Created: (DERBY-586) Provide an alternative means to shut down a database other than using getConnection()
Provide an alternative means to shut down a database other than using getConnection() -- Key: DERBY-586 URL: http://issues.apache.org/jira/browse/DERBY-586 Project: Derby Type: New Feature Components: Services Reporter: Lance Andersen Priority: Minor It would be nice to provide an alternative mechanism to shutdown a database other than calling getConnection() and having an Exception thrown. -- 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
[jira] Updated: (DERBY-247) Network Server demo program should support Derby network client driver
[ http://issues.apache.org/jira/browse/DERBY-247?page=all ] Lance Andersen updated DERBY-247: - Attachment: demo.txt attached is the proposed fix. Network Server demo program should support Derby network client driver -- Key: DERBY-247 URL: http://issues.apache.org/jira/browse/DERBY-247 Project: Derby Type: Improvement Components: Demos/Scripts Versions: 10.1.0.0 Reporter: Andrew McIntyre Assignee: Lance Andersen Priority: Minor Fix For: 10.1.0.0 Attachments: demo.txt, simpleapp.diff Currently, the Network Server demo programs require the IBM Universal JDBC Driver (JCC) for client functionality. The demo should be enhanced to also support using the Derby client driver. -- 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
[jira] Commented: (DERBY-247) Network Server demo program should support Derby network client driver
[ http://issues.apache.org/jira/browse/DERBY-247?page=comments#action_12313300 ] Lance Andersen commented on DERBY-247: -- I am just starting to look at this. Do we still need to keep this working with the DB2 driver or can we just convert this to work with the new Client driver. Network Server demo program should support Derby network client driver -- Key: DERBY-247 URL: http://issues.apache.org/jira/browse/DERBY-247 Project: Derby Type: Improvement Components: Demos/Scripts Versions: 10.1.0.0 Reporter: Andrew McIntyre Assignee: Lance Andersen Priority: Minor Fix For: 10.1.0.0 Currently, the Network Server demo programs require the IBM Universal JDBC Driver (JCC) for client functionality. The demo should be enhanced to also support using the Derby client driver. -- 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
[jira] Assigned: (DERBY-263) Remove IJ support for setting unicodeescape option.
[ http://issues.apache.org/jira/browse/DERBY-263?page=all ] Lance Andersen reassigned DERBY-263: Assign To: Lance Andersen Remove IJ support for setting unicodeescape option. --- Key: DERBY-263 URL: http://issues.apache.org/jira/browse/DERBY-263 Project: Derby Type: Sub-task Components: Tools Versions: 10.1.0.0 Reporter: Satheesh Bandaram Assignee: Lance Andersen Priority: Minor Derby doesn't support setting unicodeescape option in IJ. Need to remove the option from IJ, in addition to removing the documentation. -- 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
[jira] Resolved: (DERBY-242) DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since Derby only has limited support.
[ http://issues.apache.org/jira/browse/DERBY-242?page=all ] Lance Andersen resolved DERBY-242: -- Resolution: Fixed Patch has been reviewed and checked into the codeline. DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since Derby only has limited support. -- Key: DERBY-242 URL: http://issues.apache.org/jira/browse/DERBY-242 Project: Derby Type: Bug Components: JDBC Versions: 10.0.2.0 Environment: ALL Reporter: Satheesh Bandaram Assignee: Lance Andersen Fix For: 10.1.0.0 Derby only has partial support for retrieving generated values. Because of this, it is desirable to make DatabaseMetaData.supportsGetGeneratedKeys return FALSE. One of the restrictions include Jira entry Derby-201. Till this is fixed, we should change derby to return FALSE for this. This would also match Derby client behavior. -- 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
[jira] Assigned: (DERBY-247) Network Server demo program should support Derby network client driver
[ http://issues.apache.org/jira/browse/DERBY-247?page=all ] Lance Andersen reassigned DERBY-247: Assign To: Lance Andersen Network Server demo program should support Derby network client driver -- Key: DERBY-247 URL: http://issues.apache.org/jira/browse/DERBY-247 Project: Derby Type: Improvement Components: Demos/Scripts Versions: 10.1.0.0 Reporter: Samuel Andrew McIntyre Assignee: Lance Andersen Priority: Minor Currently, the Network Server demo programs require the IBM Universal JDBC Driver (JCC) for client functionality. The demo should be enhanced to also support using the Derby client driver. -- 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
