db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3842) Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorExternalSortJDBC30.sql" to junit.
Date Sat, 28 Mar 2009 16:22:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693467#action_12693467
] 

Tiago R. Espinha commented on DERBY-3842:
-----------------------------------------

That's an improvement at least :) now the property does get set as we can see from the output:
--------------------8<---------------------------
2009-03-28 16:04:06.418 GMT : Security manager installed using the Basic server security policy.
2009-03-28 16:04:07.063 GMT : Apache Derby Network Server - 10.6.0.0 alpha - (757793M) started
and ready to accept connections on port 1527
Sorting is booting and we have: 5
Sorting and defaultSortBufferMax is 5
---------------------8<--------------------------

The crux of it is that the statistics data still reports as doing an internal sort:
--------------------8<-------------------------------------------------------------------
Source result set:
	Sort ResultSet:
	Number of opens = 1
	Rows input = 416
	Rows returned = 416
	Eliminate duplicates = false
	In sorted order = false
	Sort information: 
		Number of rows input=416
		Number of rows output=416
		Sort type=internal
		constructor time (milliseconds) = 0
		open time (milliseconds) = 0
		next time (milliseconds) = 0
		close time (milliseconds) = 0
		optimizer estimated row count:          422.00
		optimizer estimated cost:          140.25
--------------------8<-------------------------------------------------------------------
(The table is slightly smaller now, just 416 records, but that shouldn't be an issue with
a sortBufferMax of 5)

So, I think I'm looking at two different issues here:
- This specific property can't be set using SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY();
Or in other words, it can be set but then Derby won't find it. This will probably not be an
issue for my actual test, since I do it programmatically there. Maybe this is even normal
and it was just a mistake of mine all along when testing manually.

- The other, actual issue, is that Derby still refuses to do external sorting, even when the
record count clearly exceeds the sortBufferMax. This one still remains a mystery. 


> Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorExternalSortJDBC30.sql"
to junit.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3842
>                 URL: https://issues.apache.org/jira/browse/DERBY-3842
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Junjie Peng
>            Assignee: Tiago R. Espinha
>         Attachments: derby-3842-1.patch, derby-3842-1.stat, derby-3842-tiago.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message