[
https://issues.apache.org/jira/browse/DERBY-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488294
]
Knut Anders Hatlen commented on DERBY-2118:
---
The tests ran cleanly. Committed setlimit.diff with revision
[
https://issues.apache.org/jira/browse/DERBY-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488304
]
Kristian Waagan commented on DERBY-2359:
Committed 'derby-2359-3a-visibility_changes.diff' to trunk with
[
https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488308
]
Øystein Grøvlen commented on DERBY-2540:
Knut Anders, thanks for the reference to your summary of length
[
https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen updated DERBY-2540:
---
Attachment: derby-2540.stat
derby-2540.diff
The attached patch contains the
[
https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen updated DERBY-2540:
---
Derby Info: [Patch Available]
Restructure code for Blob/Clob length in client to prepare
[
https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488344
]
Øystein Grøvlen commented on DERBY-2540:
Forgot to mention that I have run the Junit All suite with no new
[Auto-generated mail]
*tinderbox_trunk16* 527833/2007-04-12 10:22:43 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0346346 096.32% derbyall
F:3,E:173837379 0
[
https://issues.apache.org/jira/browse/DERBY-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-2506:
---
Derby Info: [Patch Available]
Adding the locator information to FD:OCA descriptor (FDODSC)
[
https://issues.apache.org/jira/browse/DERBY-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-2385:
---
Derby Info: [Patch Available]
create the stored procedures called by LOB related JDBC methods
[
https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2493:
--
Attachment: derby-2493-vector.stat
derby-2493-vector.diff
[
https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2493:
--
Derby Info: [Patch Available]
Use unsynchronized collections in BackingStoreHashtable
[
https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Nirhali resolved DERBY-2386.
-
Resolution: Fixed
No issues found on the fix.
timestampdiff function fails when using
[
https://issues.apache.org/jira/browse/DERBY-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488374
]
Rick Hillegas commented on DERBY-2193:
--
Committed derby-2193-01.diff at subversion revision 527944.
[import]
[
https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488395
]
Mayuresh Nirhali commented on DERBY-2230:
-
The assert is reproducible on trunk as well. When I tried the
Issue Subscription
Filter: Derby: JIRA issues with patch available (24 issues)
Subscriber: derby-dev
Key Summary
DERBY-2493 Use unsynchronized collections in BackingStoreHashtable
https://issues.apache.org/jira/browse/DERBY-2493
DERBY-2385 create the stored procedures
[Auto-generated mail]
*Daily* 527546/2007-04-11 18:00:26 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0347347 077.46% derbyall
F:1,E:073787377 0 518.07% suitesAll
sles
[Auto-generated mail]
*tinderbox_trunk16* 527898/2007-04-12 14:23:08 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0346346 095.82% derbyall
F:3,E:173837379 0
Mamta Satoor wrote:
If we decide to provide static interface on DataValueFactory, then the
Locale field and the RuleBasedCollator will need to be static too since
we the static interfaces will need access to RuleBasedCollator. Because
of this I am leaning more towards have non-static
[
https://issues.apache.org/jira/browse/DERBY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2537:
--
Attachment: derby2537_2.diff
This patch is an updated version of the derby2537_2.diff patch.
Mike, the following code will be part of DataValueFactory and hence it will
be part of the interface. Please let me know if I am not very clear with
what I am proposing or if you forsee problems with this logic.
if (dvd instanceof StringDataValue)
dvd =
[
https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488434
]
Kathey Marsden commented on DERBY-2541:
---
For creating the databases I am going with the JDBCDataSource
[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488438
]
Kim Haase commented on DERBY-2538:
--
Thanks, Army! I think you are right -- it really is just a matter of which JDK
[
https://issues.apache.org/jira/browse/DERBY-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2535:
---
Attachment: DERBY2535_Return_Collator_api_On_DVD_v1_stat.txt
[
https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2541:
--
Attachment: DERBY-2541_diff.txt
Attaching a patch for this issue. I found that there was
[
https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2541:
--
Attachment: DERBY-2541_stat.txt
Create initial testing framework for Junit Collation testing
[
https://issues.apache.org/jira/browse/DERBY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2296:
--
Attachment: DERBY-2296_20070412.diff
attaching a patch that appends create=true for
[
https://issues.apache.org/jira/browse/DERBY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2296:
--
Derby Info: [Patch Available]
getProperties method deprecated on ClientDataSource
[
https://issues.apache.org/jira/browse/DERBY-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2535:
---
Comment: was deleted
Make Locale available in DataValueFactory(DVF). This Locale object
[
https://issues.apache.org/jira/browse/DERBY-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488466
]
Mamta A. Satoor commented on DERBY-2535:
My earlier comment (that I just deleted) used incorrect terminology
[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-2538:
-
Attachment: DERBY-2538-2.zip
DERBY-2538-2.diff
Attaching DERBY-2538-2.diff and
[
https://issues.apache.org/jira/browse/DERBY-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2193:
-
Attachment: derby-2193-02.diff
Thanks for the feedback, Aaron. Attaching derby-2193-02.diff.
[Auto-generated mail]
*tinderbox_trunk16* 528002/2007-04-12 18:12:54 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0346346 096.12% derbyall
F:3,E:173837379 0
convert lang/scrollCursors1.sql to junit
-
Key: DERBY-2542
URL: https://issues.apache.org/jira/browse/DERBY-2542
Project: Derby
Issue Type: Task
Reporter: Kathey Marsden
Assigned
Mamta Satoor wrote:
Mike, the following code will be part of DataValueFactory and hence it
will be part of the interface. Please let me know if I am not very clear
with what I am proposing or if you forsee problems with this logic.
if (dvd instanceof StringDataValue)
dvd =
The Google summer of code proposals from Ramin Moazeni and Ravinder
Reddy for converting tests to Junit and fixing Derby bugs were accepted.
Congratulations Ramin and Ravinder and thank you for joining the effort
to maintain and improve the quality of the existing Derby code. I am
looking
[
https://issues.apache.org/jira/browse/DERBY-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488505
]
Suresh Thalamati commented on DERBY-2527:
-
Thanks Laura. My comments are below for the questions you posted.
[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488517
]
A B commented on DERBY-2538:
Thanks Kim, these look good to me.
I think there's one blip in the
I'm a bit confused about the test program
UpdateCursorTest.testVirtualMemoryHeap. This test program
appears to depend on the order of the rows returned, but
it does not contain an ORDER BY clause in the query. Here's
the code I'm looking at, from UpdateCursorTest.java:
/**
* Test the
[
https://issues.apache.org/jira/browse/DERBY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488525
]
Dag H. Wanvik commented on DERBY-2264:
--
Committed DERBY-2264-7.diff at svn 528274.
In addition to derbyall and
[
https://issues.apache.org/jira/browse/DERBY-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488524
]
Laura Stewart commented on DERBY-2527:
--
Suresh - Thank you for the responses.
#2 - There is a difference
[
https://issues.apache.org/jira/browse/DERBY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-2264:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Release Note Needed,
[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-2526:
---
Attachment: DistinctTestNotes.txt
I analyzed the DistinctTest failure in more detail, and
[
https://issues.apache.org/jira/browse/DERBY-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488527
]
Suresh Thalamati commented on DERBY-2527:
-
#2 : I agree with you. Changging the sentence to Passing a NULL
[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488531
]
Bryan Pendleton commented on DERBY-2526:
The UpdateCursorTest failure appears to be in a test
[Auto-generated mail]
*tinderbox_trunk16* 528109/2007-04-12 21:52:42 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0346346 096.09% derbyall
F:3,E:173837379 0
[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488534
]
A B commented on DERBY-2526:
Just a knee-jerk reaction to the DistinctTest failure: I wonder if the
transitive closure
[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488535
]
Bryan Pendleton commented on DERBY-2526:
It's interesting that in all three of the outerjoin.sql,
It looks like this test is failing in the current trunk without
your changes:
http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/528002-org.apache.derbyTesting.functionTests.suites.All_diff.txt
a quick scan of the tinderbox reports here:
[
https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488537
]
A B commented on DERBY-2526:
I thought that the transitive closure processing was only looking at join
conditions,
testVirtualMemoryHeap junit test fails with Virtual memory heap test failed!
Got unexpected value. expected:202 but was:103
--
Key: DERBY-2543
[
https://issues.apache.org/jira/browse/DERBY-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488538
]
Mike Matrigali commented on DERBY-2543:
---
I did a quick scan of the tinder box results and it looks like the
Mike Matrigali wrote:
I'm a bit confused about the test program
UpdateCursorTest.testVirtualMemoryHeap. This test program
appears to depend on the order of the rows returned, but
it does not contain an ORDER BY clause in the query. Here's
the code I'm looking at, from UpdateCursorTest.java:
On 4/12/07, Bryan Pendleton [EMAIL PROTECTED] wrote:
This test seems to be very sensitive to the precise query execution
strategy that is being used, but I don't see how the test is
controlling that query execution strategy.
Can somebody clarify how the test works for me?
Perhaps this
[
https://issues.apache.org/jira/browse/DERBY-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488539
]
Andrew McIntyre commented on DERBY-2543:
It is clear from the comments in the previous test that the row
[
https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488545
]
Dag H. Wanvik commented on DERBY-2540:
--
I'll have a look at this one.
Restructure code for Blob/Clob length
[Auto-generated mail]
*tinderbox_trunk16* 528282/2007-04-13 01:32:33 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0346346 095.62% derbyall
F:2,E:073937391 0
As Mike pointed out, this test has been failing in the nightlies, so
it might not be your change that is causing the failure.
Thanks Andrew and Mike! That was very helpful information.
bryan
Mike, I will start working on item 1. As for items 2 and 3, more
discussion/research needs to go into them.
Mamta
On 4/12/07, Mike Matrigali [EMAIL PROTECTED] wrote:
Mamta Satoor wrote:
Mike, the following code will be part of DataValueFactory and hence it
will be part of the interface.
SecurityPolicyReloadingTest( )junit.framework.AssertionFailedError: Policy
file changed. Should not be able to read the property.
--
Key: DERBY-2544
[
https://issues.apache.org/jira/browse/DERBY-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488568
]
Mike Matrigali commented on DERBY-2544:
---
I did a quick by hand scan and it looks like the test has been
testModifiesSql(org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest)junit.framework.ComparisonFailure:
Unexpected SQL state. expected:3800[0] but was:3800[1]
[
https://issues.apache.org/jira/browse/DERBY-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2545:
--
The changes for the first tinderbox run that I saw the error in were:
Changes from 527698/527698
When you go to the full history page
(http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/index_all.html)
It only lists derbyall failures, making it sort of hard to track down
suite failures, I had to click on 0 failure cases. It is too bad
but I don't think there
63 matches
Mail list logo
