Hi folks, long time no see. :)I think I'm ready to start doing some work on Derby again (not full time, but more than zero time ;o). I was thinking of DERBY-653, which Rick H created and then closed himself during a discussion in October. I think it would be nice if Derby behaved correctly
+1
Øyvind (still not productive on Derby, will be getting up to speed at Google for a while...)
this point: if Derby
works today with CLDC configuration.
No. CLDC lacks a number of essential features which Derby relies on
(such as application-controlled class loading). I don't expect Derby to
support CLDC in the near future.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Versions: 10.1.2.1
Reporter: Oyvind Bakksjo
A newly created database will contain the following schemas:
NULLID
SQLJ
SYS
SYSCAT
SYSCS_DIAG
SYSCS_UTIL
SYSFUN
SYSIBM
SYSPROC
SYSSTAT
These should be documented, at least
Derby varies: A
soccer team, a city in England, horse racing, a hat, more?
But I don't object enough to veto the logo vote. ;)
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
exclusively of
programmers to create artwork.
+1 on all of the above.
--
Oyvind Bakksjo
the word about
Derby when I'm on the inside.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
[EMAIL PROTECTED] wrote:
The logic you write
for creating a DataSource object based on the information in a JDNC
JDNC? That's an amazing typo. JNDI!
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
with.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
, but I don't think that's an issue. People write code in
editors, and usually set up the editors to display a 4-character
indentation for the tab characters.
:filetype indent on
:set softtabstop=4
:set shiftwidth=4
:set expandtab
:set ic
--
Oyvind Bakksjo
Sun Microsystems, Database
Lance J. Andersen wrote:
I am not fond of a Singleton of a SQLException but that is just me.
You would at least need to have one per thread.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
other in
unpredictable ways.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
have used the create exception trick earlier to get the current stack
trace, and seemed to recall that I had to actually throw-catch it to get
the stack trace. But that can't be the case then.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http
[ http://issues.apache.org/jira/browse/DERBY-297?page=all ]
Oyvind Bakksjo updated DERBY-297:
-
Attachment: derbyhatlogo-lettersaligned.png
Maybe someone who's more skilled with graphics than I am can take the hat idea,
place all the characters
tried:
-bash-2.05b$ cd /www/db.apache.org/derby
-bash-2.05b$ svn update
svn: Can't open file '.svn/lock': Permission denied
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
Jean T. Anderson wrote:
What groups are you in, Oyvind? You need to be in 'db' -- are you?
I thought it might be a group thing.
-bash-2.05b$ groups
bakksjo apcvs incubator
Exactly.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog
In the table at
http://db.apache.org/derby/integrate/misc.html#Products+by+Type
Derby Network Client is listed under ODBC Drivers, not under JDBC
Drivers. Surely, this must be a mistake. I'll correct it (unless
someone yells :).
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
to the
Products by Type section of the Summary page?
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
that would help. Does it
at least do the html build?
Yes, it does.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
: 2096440 5877961508644
ant -version
Apache Ant version 1.6.2 compiled on July 16 2004
java -version
java version 1.4.2_02
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
Reporter: Oyvind Bakksjo
purposes? Please make a note of the platform, Ant version, full JDK
version, and any relevant machine info (like total physical RAM).
Entered DERBY-710 for this.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
[
http://issues.apache.org/jira/browse/DERBY-31?page=comments#action_12357683 ]
Oyvind Bakksjo commented on DERBY-31:
-
Updated documentation which stated setQueryTimeout was not implemented.
Sendingsrc/ref/rrefjdbc40794.dita
Transmitting file
[ http://issues.apache.org/jira/browse/DERBY-31?page=all ]
Oyvind Bakksjo updated DERBY-31:
Comment: was deleted
Statement.setQueryTimeout() support.
Key: DERBY-31
URL: http://issues.apache.org
executing this line:
.../DITA-OT1.0.1/ditatargets.xml:60: The following error occurred while
executing this line:
java.lang.OutOfMemoryError
Has anyone else seen this? Am I doing something wrong? I'm using ant
1.6.2 and JDK 1.4.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim
: Oyvind Bakksjo
Try connecting with e.g. 'jdbc:derby://localhost/foo bar;create=true' - the
database directory created will be named foo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12357597 ]
Oyvind Bakksjo commented on DERBY-506:
--
Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java
Sendingjava/client/org/apache/derby/client/am
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo resolved DERBY-506:
--
Resolution: Fixed
Had to disable some testing because of DERBY-694
Implement Statement.setQueryTimeout in the Client Driver
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo closed DERBY-506:
Implement Statement.setQueryTimeout in the Client Driver
Key: DERBY-506
URL
Re-enable test which was disabled in DERBY-506 commit
-
Key: DERBY-705
URL: http://issues.apache.org/jira/browse/DERBY-705
Project: Derby
Type: Test
Components: Test
Reporter: Oyvind Bakksjo
Priority
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo updated DERBY-506:
-
Attachment: (was: DERBY-506_PRE.diff)
Implement Statement.setQueryTimeout in the Client Driver
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo updated DERBY-506:
-
Attachment: DERBY-506.status
Implement Statement.setQueryTimeout in the Client Driver
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo updated DERBY-506:
-
Attachment: DERBY-506.diff
Diff from revision 332067.
Implement Statement.setQueryTimeout in the Client Driver
enhancements for XPATH/XQuery support
13. setQueryTimeout for Derby client
14. ALTER Table DROP COLUMN
Satheesh
Are 5 and 13 duplicates, or is 5 a different kind of timeout?
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
Type: Bug
Components: Network Client
Versions: 10.1.1.1
Reporter: Oyvind Bakksjo
Priority: Minor
Scenario:
Autocommit off. Have two prepared statements, calling executeQuery() on both,
giving me two result sets. Can fetch data from both with next(). If one
statement
[ http://issues.apache.org/jira/browse/DERBY-694?page=all ]
Oyvind Bakksjo updated DERBY-694:
-
Attachment: StatementRollbackTest.java
Attached program which demonstrates the bug.
Statement exceptions cause all the connection's result sets to be closed
[ http://issues.apache.org/jira/browse/DERBY-663?page=all ]
Oyvind Bakksjo resolved DERBY-663:
--
Fix Version: 10.2.0.0
Resolution: Fixed
Test of derby fails because difference in encoding of eol make sizes of test
data files different
there
(somewhere).
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
fernende
What happens if you execute values replace('banana', 'an', 'ul')? How
does VARCHAR(50) map to a java char?
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
[
http://issues.apache.org/jira/browse/DERBY-663?page=comments#action_12356634 ]
Oyvind Bakksjo commented on DERBY-663:
--
Sending
java/testing/org/apache/derbyTesting/functionTests/testData/ImportExport/position_info.del
Transmitting file data
changes on the files, but no actual content diffs.
Now, when the patch is *committed*, suddenly all the files' content
changes. Thus, these failures were not caught before committing, but
after. I'm sorry about the consequences for you all, and I'll go ahead
and try to fix the issues.
--
Oyvind
Subversion does not understand that the diff is
because of a property change, and that's a pity. Subversion is, with
respect to the eol-style property change, as stupid as CVS is to
moving/renaming files. :o(
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http
[
http://issues.apache.org/jira/browse/DERBY-663?page=comments#action_12356502 ]
Oyvind Bakksjo commented on DERBY-663:
--
Sending
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/aclob.txt
Sending
java/testing/org/apache
svn does diffing and patching when
invoking the merge subcommand?
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
that I can close and resolve DERBY-330?
Yes.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
... What's useful behaviour depends
on the application and its needs. If you don't need update locks on the
entire result set, the usefulness of such a behaviour is negative,
since it only reduces concurrency and, as such, overall performance.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology
.
Committed revision 329187.
Any chocolate for contributing the largest patch? ;o)
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
= svn:eol-style=LF
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
will complain - as I understand
it, doing the whole DERBY-330 thing potentially creates a huge diff,
which may cause conflicts when other developers update with local
modifications. But I suspect there will never be a Good Time to do this.
I think I'll just fix the scripts first.
--
Oyvind
have to deal
with CRLF.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
have svn:eol-style set to native, and
svn:keywords set to Id. Auto-prop support is perhaps the handiest
property related tool in the Subversion toolbox. See the section called
“Config” for more about configuring that support.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
native' property setting.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
' property setting.
Hm. Have a look at this file:
trunk/java/testing/org/apache/derbyTesting/functionTests/testData/ImportExport/mixednl.del
What's the correct eol-style for this one?? :o)
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog
)
I agree.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
/store/TurnsReadOnly.java
Adding
java/testing/org/apache/derbyTesting/functionTests/tests/store/TurnsReadOnly_app.properties
Sending
java/testing/org/apache/derbyTesting/functionTests/tests/store/copyfiles.ant
Transmitting file data
Committed revision 325896.
--
Oyvind Bakksjo
Sun
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331714 ]
Oyvind Bakksjo commented on DERBY-506:
--
Sending the EXCSQLSET when the JDBC call [to Statement.setQueryTimeout()] is
made would cause an additional round-trip between
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331738 ]
Oyvind Bakksjo commented on DERBY-506:
--
I understand your points, but with regards to setQueryTimeout(), I honestly
think you're making too much of this. ;-) To make my
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo updated DERBY-506:
-
Attachment: DERBY-506_PRE.diff
This patch is not intended for inclusion, it just illustrates the idea and is a
basis for discussion about the approach
Oyvind Bakksjo (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-506?page=all ]
Oyvind Bakksjo updated DERBY-506:
-
Attachment: DERBY-506_PRE.diff
I'd like to get some feedback on this approach. Since the DRDA protocol
doesn't have any field
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo resolved DERBY-579:
--
Resolution: Fixed
Query timeout set for one statement may affect other statements with the same
SQL string
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331272 ]
Oyvind Bakksjo commented on DERBY-587:
--
OK, I'll commit it.
Providing JDBC 4.0 support for derby
Key: DERBY-587
be
made to run faster?
It now runs in 29 seconds on my machine, I hope that's satisfactory. :)
Satheesh
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: (was: DERBY-579.svn.diff)
Query timeout set for one statement may affect other statements with the same
SQL string
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: (was: DERBY-579.svn.status)
Query timeout set for one statement may affect other statements with the same
SQL string
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: DERBY-579.svn.status
Query timeout set for one statement may affect other statements with the same
SQL string
[
http://issues.apache.org/jira/browse/DERBY-579?page=comments#action_12331188 ]
Oyvind Bakksjo commented on DERBY-579:
--
Last attached diff relates to svn repository version 293374.
Query timeout set for one statement may affect other statements
this
approach and it works perfectly.
Using this technique, I don't have to rely on big data volumes, so I
should be able to squeeze the test's running time down to less than a
minute, at the same time making it completely predictable on any
hardware, fast or slow. Thanks for the great idea!
--
Oyvind
the test run faster. The problem is that it's hard to tune the size of
the tables so you're guaranteed that the fetching of some rows will
take longer than the timeout value.
I'll also look at adding a testcase for the bug that this patch addresses.
--
Oyvind Bakksjo
Sun Microsystems, Database
forward, this will allow
developers to write assertion-based tests. For the moment, this will
not change the existing test harness.
+1
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Trondheim, Norway
http://weblogs.java.net/blog/bakksjo/
Oyvind Bakksjo (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: DERBY-579.svn.diff
If nobody objects by end of business today (any timezone), I will commit
this patch
build should be the build used in the testing
reported at http://www.multinet.no/~solberg/public/Apache/Derby/index.html/
That way, people can download and use a nightly build at their own risk,
but they can also see what tests the build has passed/failed.
--
Oyvind Bakksjo
Sun Microsystems
: Bug
Components: SQL
Reporter: Oyvind Bakksjo
Assigned to: Oyvind Bakksjo
Priority: Minor
Fix For: 10.2.0.0
The timeout is being set on the class GenericPreparedStatement, but this
represents a statement plan and can be shared across multiple
connections (through the statement
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: DERBY-579.svn.status
Query timeout set for one statement may affect other statements with the same
SQL string
[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
-
Attachment: DERBY-579.svn.diff
This patch fixes the bug as proposed by Dan Debrunner (pass the timeout into
the execute method
[ http://issues.apache.org/jira/browse/DERBY-574?page=all ]
Oyvind Bakksjo closed DERBY-574:
Fix Version: (was: 10.2.0.0)
Resolution: Duplicate
Per JDBC connection timeouts are incorrectly set
is still open when I get back
I'll look into fixing it.
--
Oyvind Bakksjo
Sun Microsystems, Database Technology Group
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43419 / +47 73842119, Fax: +47 73842101
Jean T. Anderson wrote:
OK, Derby committers, you all have karma to the db site module.
Oyvind and Jeremy, please try your commit again and let me know.
It worked for me now.
--
Øyvind Bakksjø
Sun Microsystems, Database Technology Group
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43419
[ http://issues.apache.org/jira/browse/DERBY-544?page=all ]
Oyvind Bakksjo closed DERBY-544:
Resolution: Fixed
Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS
[
http://issues.apache.org/jira/browse/DERBY-544?page=comments#action_12322775 ]
Oyvind Bakksjo commented on DERBY-544:
--
I'll go ahead and commit it.
Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS
: 10.1.1.0
Reporter: Oyvind Bakksjo
Assigned to: Oyvind Bakksjo
Priority: Trivial
Fix For: 10.2.0.0
The admin guide at
http://db.apache.org/derby/docs/10.1/adminguide/cadminappsclienttracing.html
lists the various tracing constants for the Network Client.
It lists the value
[ http://issues.apache.org/jira/browse/DERBY-544?page=all ]
Oyvind Bakksjo updated DERBY-544:
-
Attachment: DERBY-544.diff
DERBY-544.status
Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS
[ http://issues.apache.org/jira/browse/DERBY-463?page=all ]
Oyvind Bakksjo resolved DERBY-463:
--
Fix Version: 10.2.0.0
Resolution: Fixed
Committed revision 233487.
Successive writes to a java.sql.Blob.setBinaryStream(long) seem to reset
Satheesh Bandaram wrote:
I agree with these comments... In fact, I added similar comments to the
bug on 14th Aug. In case Jira didn't send that message out, here it is:
I would like to hear reasoning behind this new feature request. I
see following issues with the suggestion:
1)
[ http://issues.apache.org/jira/browse/DERBY-505?page=all ]
Oyvind Bakksjo closed DERBY-505:
Resolution: Won't Fix
No interest in this functionality. Use JDBC instead.
Add system procedure to allow setting statement timeout
[
http://issues.apache.org/jira/browse/DERBY-463?page=comments#action_12319005 ]
Oyvind Bakksjo commented on DERBY-463:
--
The bugfix looks ok.
My comments do not concern the fix, but the patch itself:
- BlobOutputStream.java: The System.arraycopy
Fernanda Pizzorno (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-463?page=all ]
Fernanda Pizzorno updated DERBY-463:
Attachment: DERBY-463.diff
Change method write (byte[], int, int) in
Components: Documentation
Versions: 10.1.1.0
Reporter: Oyvind Bakksjo
Priority: Minor
Using Class.forName(driver name).newInstance() is the recommended way to
load and instantiate the JDBC driver, but the documentation does not contain
the .newInstance() part.
Pointers:
http
Reporter: Oyvind Bakksjo
Assigned to: Oyvind Bakksjo
Priority: Minor
Propose to add a system procedure:
SYSCS_UTIL.SYSCS_SET_STATEMENT_TIMEOUT(INT)
This procedure will enable the query timeout functionality not only through
JDBC, but also through SQL. I suggest the following semantics
Reporter: Oyvind Bakksjo
Assigned to: Oyvind Bakksjo
Currently, the Embedded Driver supports Statement.setQueryTimeout(), but the
Client Driver does not. The Client Driver should be enhanced and match the
Embedded Driver.
For this, we need to transfer the timeout value from the client
David Van Couvering wrote:
Hi, Oyvind, you may have already done this, but can you linke this to
DERBY-310?
That was my intention, yes. Thanks for reminding me. :) Done now.
--
Øyvind Bakksjø
Sun Microsystems, Database Technology Group
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43419 /
Daniel John Debrunner wrote:
[EMAIL PROTECTED] wrote:
Currently, the Derby client contains a client-side implementation of
setQueryTimeout; using a TimerTask to invoke Statement.cancel() on the
client side. First of all, cancel() is not implemented, so this doesn't
work. Furthermore, we should
Currently, the Derby client contains a client-side implementation of
setQueryTimeout; using a TimerTask to invoke Statement.cancel() on the
client side. First of all, cancel() is not implemented, so this doesn't
work. Furthermore, we should use the server-side mechanism we now have
for
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
I had to re-run the tests because the patch messed up on one file, but
now StmtCloseFunTest fails for me with this patch.
*** Start: StmtCloseFunTest jdk1.4.2 derbyall:jdbc20 2005-06-28 22:08:57 ***
2a3
Daniel John Debrunner wrote:
I think delaying the comment is fine.
I'm planning to commit this change before the end of this week, assuming
all the tests run for me.
Great!
One thing I do need is confirmation that the
copyright dates are correct in the files you've added. Some of them have
Daniel John Debrunner wrote:
Oyvind Bakksjo (JIRA) wrote:
Hi Dan, thanks for reviewing this patch so quickly.
I am fully aware of and share you concern for the performance impact of
creating all the TimerTask objects.
It is far from ideal.
The problem is that the Timer class _forces_
Daniel John Debrunner wrote:
Oyvind Bakksjo (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-31?page=all ]
Oyvind Bakksjo updated DERBY-31:
Attachment: DERBY-31.svn.status
DERBY-31.svn.diff
derbyall_report.txt
Kathey Marsden wrote:
[EMAIL PROTECTED] wrote:
Shreyas, would you mind deleting the old patch to avoid confusion. Also
I was thinking you might be interested in reviewing Oyvind's patch since
you have shown interest in this issue in the past. Perhaps Oyvind would
be willing to review your
[
http://issues.apache.org/jira/browse/DERBY-31?page=comments#action_12313431 ]
Oyvind Bakksjo commented on DERBY-31:
-
Hi Dan, thanks for reviewing this patch so quickly.
I am fully aware of and share you concern for the performance impact of
creating
[ http://issues.apache.org/jira/browse/DERBY-31?page=all ]
Oyvind Bakksjo updated DERBY-31:
Attachment: svn.diff
Output of the 'svn diff' command.
Statement.setQueryTimeout() support.
Key: DERBY-31
[ http://issues.apache.org/jira/browse/DERBY-31?page=all ]
Oyvind Bakksjo updated DERBY-31:
Attachment: svn.status
Output of the 'svn status' command.
Statement.setQueryTimeout() support.
Key: DERBY-31
I have attached a patch for Statement.setQueryTimeout() to the DERBY-31
JIRA issue. I hope somebody will have time to review it.
I'm currently running derbyall, which seems to run fine, except that it
takes very long on my machine, and I'm leaving for the weekend, so I
will not have the time
1 - 100 of 112 matches
Mail list logo
