[jira] Created: (DERBY-120) Date string returned from SELECT against Network Server is incorrect

Date string returned from SELECT against Network Server is incorrect Key: DERBY-120 URL: http://issues.apache.org/jira/browse/DERBY-120 Project: Derby Type: Bug Components: Network Server Envir

[jira] Created: (DERBY-119) Add ALTER TABLE option to change column from NULL to NOT NULL

Add ALTER TABLE option to change column from NULL to NOT NULL -- Key: DERBY-119 URL: http://issues.apache.org/jira/browse/DERBY-119 Project: Derby Type: New Feature Reporter: Bernd Ruehlicke There was

Re: Question on Read-only resultset and updateXXX and updateRow methods

I will discuss this with the JDBC 4 EG. As you point out this is not clear in the javadocs or the current JDBC 3 spec. We are in the process of trying to clean up some areas in the spec. This is another reasonable candidate. Regards Lance Satheesh Bandaram wrote: I think throwing error in the

Re: Question on Read-only resultset and updateXXX and updateRow methods

I think throwing error in the updateInt() method early is good. Why wait till updateRow()? Also the JCC driver (Derby's current client JDBC driver) throws error for the updateInt(), so both embedded driver and the network driver would behave the same. Satheesh Mamta Satoor wrote: >Hi, > >Unless

Question on Read-only resultset and updateXXX and updateRow methods

Hi, Unless I have missed it in the JDBC spec or apis, I don't think JDBC documentation says when a driver should throw an exception for update attempt on a read-only ResultSet. In following eg, should the driver throw exception that update api not permitted on read-only resultsets at rs.updateI

Bulk load of large data sets

Hi, all. I get a Java OutOfMemory error when I try to load a large table into a derby database using the bulk load stored procedure SYSCS_UTIL.SYSCS_IMPORT_TABLE. It is a 5GB table. It appears that this procedure tries to load the entire table into cache before it checkpoints it? Any advice woul

RESEND: possible resource leak in either Derby DRDA or IBM DB2 Universal JDB

=> > Although I cannot (yet) identify where the problem is, I believe > One potential problem is that with JCC and Network Server, prepared > statements will not get cleaned up unless they are explicitly closed. > A good check to see if this is the problem is to run > NetworkServerControl runtimei

Re: Date formatting with Network Server

Army wrote: Question regarding date formatting in the Network Server: System.out.println(java.sql.Date.valueOf("0001-01-01")); [snip] So my question is three-fold: 1) The Java definition for java.sql.Date.toString() says: "Formats a date in the date escape format -mm-dd". So as far as I c

Date formatting with Network Server

Question regarding date formatting in the Network Server: System.out.println(java.sql.Date.valueOf("0001-01-01")); With a Sun JVM, the above line will print "0001-01-01". With an IBM JVM, it will print "1-01-01". The difference is apparently in the implementation of the "toString()" meth

[PATCH] test harness skip derbynet suite if no db2jcc.jar

Hi, Attached is a patch that will cause test suites run with the property 'framework=DerbyNet' to be skipped if the IBM Universal JDBC Driver is not available. Currently the only suites run like that are the *derbynetmats suites. Reason for this skipping is so folks that folks not running with

Re: RESEND: possible resource leak in either Derby DRDA or IBM DB2 Universal JDBC Driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Cable wrote: [snip] > > Although I cannot (yet) identify where the problem is, I believe there > must be some problem in either the DB2 client or the derby server DRDA > implementation ... > > anyone got any ideas/comments? > > - Larry Cable