[ http://issues.apache.org/jira/browse/DERBY-1392?page=all ]
Mike Matrigali resolved DERBY-1392:
---
Fix Version: 10.1.3.1
Resolution: Fixed
I merged/resolved conflicts from this change in the trunk to the 10.1 branch
and committed
as follows:
[ http://issues.apache.org/jira/browse/DERBY-1413?page=all ]
Mike Matrigali updated DERBY-1413:
--
Assign To: (was: Mike Matrigali)
As described above I looked at creating a message for this, but my take is that
one exists. I am taking myself off
[ http://issues.apache.org/jira/browse/DERBY-1429?page=all ]
Mike Matrigali updated DERBY-1429:
--
Component: Services
(was: Store)
This issue should be handled by the monitor, not the store.
Additional vulnerability to
[ http://issues.apache.org/jira/browse/DERBY-1343?page=all ]
Mike Matrigali updated DERBY-1343:
--
Component: (was: Store)
this is an issue with the system catalogs, from discussions on list it looks
like not a store issue.
It is possible to have
[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ]
Mike Matrigali updated DERBY-1156:
--
i reviewed and tested reencrypt_3.diff patch. it looks fine, i will let you
commit. Still would like to see more testing, especially exercising the abort
[ http://issues.apache.org/jira/browse/DERBY-1428?page=all ]
Mike Matrigali updated DERBY-1428:
--
Component: Services
(was: Store)
changing component from store to services. This is really a monitor issue.
Generating derby
[ http://issues.apache.org/jira/browse/DERBY-1410?page=all ]
Mike Matrigali updated DERBY-1410:
--
Fix Version: 10.2.0.0
Assign To: Mike Matrigali
SQL State DATA_SQLDATA_READ_ILLEGAL_ACCESS_EXCEPTION does not have a matching
message
[ http://issues.apache.org/jira/browse/DERBY-1410?page=all ]
Mike Matrigali resolved DERBY-1410:
---
Resolution: Fixed
m1_142:88svn commit
Sendingjava\engine\org\apache\derby\loc\messages_en.properties
Transmitting file data .
Committed
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali updated DERBY-937:
-
Fix Version: 10.2.0.0
committed
Instability in wisconsin test
-
Key: DERBY-937
URL:
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali updated DERBY-937:
-
committed change to trunk:
r418108 | mikem | 2006-06-29 11:27:51 -0700 (Thu, 29 Jun 2006) | 16 lines
DERBY-937, committing change by Andreas Korneliussen.
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali resolved DERBY-937:
--
Resolution: Fixed
I am closing this intermittent bug with fix committed as: 418108. If it
shows up again file a new issue with the new details.
[ http://issues.apache.org/jira/browse/DERBY-1017?page=all ]
Mike Matrigali updated DERBY-1017:
--
Component: SQL
(was: Network Server)
The most recent comment says this reproduces in embedded, so not a network
server issue. Setting
[ http://issues.apache.org/jira/browse/DERBY-1453?page=all ]
Mike Matrigali updated DERBY-1453:
--
Component: Network Client
Network Server
jdbcapi/blobclob4BLOB.java fails with 10.1 client and 10.2 server
[ http://issues.apache.org/jira/browse/DERBY-1450?page=all ]
Mike Matrigali updated DERBY-1450:
--
Component: Test
jdbcapi/parameterMetaDataJdbc30.java fails with 10.1 client and 10.2 server
[ http://issues.apache.org/jira/browse/DERBY-1387?page=all ]
Mike Matrigali updated DERBY-1387:
--
Component: Services
for lack of a better component made it services.
Add JMX extensions to Derby
---
Key:
[ http://issues.apache.org/jira/browse/DERBY-1452?page=all ]
Mike Matrigali updated DERBY-1452:
--
Component: Test
jdbcapi/resultset.java fails with 10.1 client and 10.2 server
-
[ http://issues.apache.org/jira/browse/DERBY-1458?page=all ]
Mike Matrigali updated DERBY-1458:
--
Component: Build tools
Add MessageBundleTest to build script to verify that there are no orphaned
message ids
[ http://issues.apache.org/jira/browse/DERBY-1053?page=all ]
Mike Matrigali updated DERBY-1053:
--
Component: Regression Test Failure
stress.multi test on ibm142 in SANE builds fails with ASSERTION at
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali updated DERBY-1248:
--
The following is from looking at the test335 failure.
My interpretation so far is that the online backup has data page changes
without the corresponding log
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali updated DERBY-1248:
--
Attachment: derby_335.log
This is full recovery debug log from the 335 repro.
Assert failure in BasePage.shiftUp() when running
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali updated DERBY-1248:
--
After a bit more thought the code can not throw an assert during undo based on
page versions. It may
be perfectly valid to appy a version 400 undo record to
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali updated DERBY-1248:
--
After looking at the test5.zip, I believe I understand what is going on. The
original database has a single log file file: log1.dat.
It's last record is
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali reassigned DERBY-1248:
-
Assign To: Mike Matrigali
Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql
[ http://issues.apache.org/jira/browse/DERBY-132?page=all ]
Mike Matrigali closed DERBY-132:
in place table/index compress which returns space to OS
---
Key: DERBY-132
URL:
[ http://issues.apache.org/jira/browse/DERBY-662?page=all ]
Mike Matrigali closed DERBY-662:
during crash recovery of a drop table, on case insensitive files systems
derby may delete wrong file
[ http://issues.apache.org/jira/browse/DERBY-670?page=all ]
Mike Matrigali closed DERBY-670:
improve space reclamation from deleted blob/clob columns which are bigger
than a page
[ http://issues.apache.org/jira/browse/DERBY-741?page=all ]
Mike Matrigali closed DERBY-741:
row estimates from btree code can sometimes return more row than exist in
table
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali closed DERBY-715:
lock deadlocks sometimes reported as lock timeouts
--
Key: DERBY-715
URL:
[ http://issues.apache.org/jira/browse/DERBY-904?page=all ]
Mike Matrigali closed DERBY-904:
big decimal error diff in derbyall lang/procedure test run in the
DerbyNetClient - jdk1.3 specific
[ http://issues.apache.org/jira/browse/DERBY-888?page=all ]
Mike Matrigali closed DERBY-888:
improve performance of page allocation
--
Key: DERBY-888
URL:
[ http://issues.apache.org/jira/browse/DERBY-906?page=all ]
Mike Matrigali closed DERBY-906:
parameterMapping test in DerbyAll nightly regression under DerbyNetClient,
specific to jdk1.3.1
[ http://issues.apache.org/jira/browse/DERBY-905?page=all ]
Mike Matrigali closed DERBY-905:
derbyall nightly failure in LOBTest running under DerbyNetClient - jdk131
specific
[ http://issues.apache.org/jira/browse/DERBY-907?page=all ]
Mike Matrigali closed DERBY-907:
regression test failure in RecoveryAfterBackup on wssd5.6 ibm jvm (j2me)
[ http://issues.apache.org/jira/browse/DERBY-1187?page=all ]
Mike Matrigali closed DERBY-1187:
-
defragment of inplace compress pass for described dataset is not freeing up
empty pages.
[ http://issues.apache.org/jira/browse/DERBY-1408?page=all ]
Mike Matrigali closed DERBY-1408:
-
derbyall/jdbcapi/ScrollResultSetTest failed
---
Key: DERBY-1408
URL:
[ http://issues.apache.org/jira/browse/DERBY-1189?page=all ]
Mike Matrigali closed DERBY-1189:
-
latch self deadlock when running inplace compress
-
Key: DERBY-1189
URL:
full table scans of tables which don't use indexes, which have blobs, but don't
reference blob data still read all pages of the table
-
Key: DERBY-1506
[ http://issues.apache.org/jira/browse/DERBY-1506?page=all ]
Mike Matrigali updated DERBY-1506:
--
Description:
A full table scan that does not use an index always reads every allocated page
of the table through the cache. In two cases
this means
[ http://issues.apache.org/jira/browse/DERBY-1506?page=all ]
Mike Matrigali updated DERBY-1506:
--
The following approach was suggested by [EMAIL PROTECTED]
Maybe a simple fix would be to segment the pages in the container. Store the
relational information
[ http://issues.apache.org/jira/browse/DERBY-1506?page=all ]
Mike Matrigali updated DERBY-1506:
--
I haven't thought about this much, but the following approaches all would solve
the problem, some easier than others,
these address the long column issue (I
improve store costing of fetch of single row where not all columns are fetched.
---
Key: DERBY-1508
URL: http://issues.apache.org/jira/browse/DERBY-1508
Project: Derby
Type: Improvement
[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ]
Mike Matrigali updated DERBY-1156:
--
Here are my comments on review of the reencrypt_4.diff, also I am running
storeall but it has not finished yet.:
minor typo's:
XactFactory.java line 835 -
[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ]
Mike Matrigali updated DERBY-1156:
--
storeall ran fine with sun jdk1.4.2 on xp - with patch reencrypt_4
allow the encrypting of an existing unencrypted db and allow the
re-encrypting of an
[ http://issues.apache.org/jira/browse/DERBY-1466?page=all ]
Mike Matrigali reassigned DERBY-1466:
-
Assignee: Sunitha Kambhampati
Network Server should flush the PrintWriter after console output
[ http://issues.apache.org/jira/browse/DERBY-1227?page=all ]
Mike Matrigali updated DERBY-1227:
--
I will look at committing the backport to 10.1
Network Server should not use the underlying embedded prepared statement when
accessing a
[ http://issues.apache.org/jira/browse/DERBY-1227?page=all ]
Mike Matrigali updated DERBY-1227:
--
Fix Version/s: 10.1.4.0
committed patch to 10.1 branch:
m101_142:117svn commit
Sendingjava\drda\org\apache\derby\impl\drda\DRDAConnThread.java
[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ]
Mike Matrigali updated DERBY-1373:
--
Committed the 10.1_explicitsvnadd_derby1373.diff.txt patch to the 10.1 branch:
m101_142:149svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ]
Mike Matrigali updated DERBY-1373:
--
Fix Version/s: 10.1.4.0
Encrypted databases cannot be booted using the jar subprotocol (and possibly
also using http/https/classpath)
[ http://issues.apache.org/jira/browse/DERBY-1574?page=all ]
Mike Matrigali updated DERBY-1574:
--
If at all possible always include the full stack trace from derby.log when
reporting a bug. Here is the
stack from the original problem against the trunk
[ http://issues.apache.org/jira/browse/DERBY-1574?page=all ]
Mike Matrigali updated DERBY-1574:
--
AS posted to list:
A B commented on DERBY-1574:
For the record, I ran the simple repro against an early version of
10.1(10.1.2.3)
[ http://issues.apache.org/jira/browse/DERBY-1640?page=all ]
Mike Matrigali updated DERBY-1640:
--
This is the kind of diff that is usally caused by some change to system
catalogs that is reflected in a newly created database (adding/removing system
[ http://issues.apache.org/jira/browse/DERBY-1640?page=all ]
Mike Matrigali updated DERBY-1640:
--
Component/s: Regression Test Failure
Instability in XATest
-
Key: DERBY-1640
URL:
[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ]
Mike Matrigali resolved DERBY-1248.
---
Fix Version/s: 10.2.0.0
Resolution: Fixed
committed fix to trunk:
m3_142:80svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1641?page=all ]
Mike Matrigali updated DERBY-1641:
--
Component/s: SQL
Adding SQL as component. Without debugging it is only a guess, but in my
experience this kind of problem is
almost always a SQL
[ http://issues.apache.org/jira/browse/DERBY-1661?page=all ]
Mike Matrigali updated DERBY-1661:
--
I have reviewed and committed this change. To me I think this is a reasonable
1st step to addressing this
issue, it should avoid most errors when doing large
[ http://issues.apache.org/jira/browse/DERBY-1660?page=all ]
Mike Matrigali updated DERBY-1660:
--
committed the patch with the test for this issue: svn 430799
SYSCS_BULK_INSERT fails with syntax error at PROPERTIES clause.
[ http://issues.apache.org/jira/browse/DERBY-1653?page=all ]
Mike Matrigali updated DERBY-1653:
--
We could really use some more information about this report. Could you define
what you mean when you
say the whole DB gets corrupt? Does it mean you can no
[ http://issues.apache.org/jira/browse/DERBY-1652?page=all ]
Mike Matrigali updated DERBY-1652:
--
Derby Info: [Patch Available, Existing Application Impact, Release Note
Needed] (was: [Release Note Needed, Patch Available, Existing Application
[ http://issues.apache.org/jira/browse/DERBY-1691?page=all ]
Mike Matrigali updated DERBY-1691:
--
Component/s: Regression Test Failure
jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6
[ http://issues.apache.org/jira/browse/DERBY-1693?page=all ]
Mike Matrigali updated DERBY-1693:
--
I agree, my guess is that we are trying to print out the whole blob/clob in the
log statement text. This is
very unlikely what the user wants. And in the
out of memory failures with the jdbcapi junit suite when run under
derbynetclientsmats suite
Key: DERBY-1701
URL: http://issues.apache.org/jira/browse/DERBY-1701
[ http://issues.apache.org/jira/browse/DERBY-1652?page=all ]
Mike Matrigali updated DERBY-1652:
--
I reproduced the out of memory on my machine in a clean codeline so do not
believe it is caused by this
patch. I also have reported DERBY-1701 for those out
[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]
Mike Matrigali updated DERBY-1633:
--
Derby Info: [Existing Application Impact, Regression] (was: [Regression,
Existing Application Impact])
for what it is worth d1633_v2.patch passed a full
[ http://issues.apache.org/jira/browse/DERBY-1713?page=all ]
Mike Matrigali updated DERBY-1713:
--
Summary: Memory do not return to the system after Shuting down derby
10.2.1.0, following an out of memory event (was: Memory do not return to the
system
[ http://issues.apache.org/jira/browse/DERBY-1714?page=all ]
Mike Matrigali updated DERBY-1714:
--
Component/s: SQL
(was: Store)
huge single insert statements fail with JVM error due to size of generated
method
[ http://issues.apache.org/jira/browse/DERBY-1691?page=all ]
Mike Matrigali reopened DERBY-1691:
---
I am also seeing the following diffs in my nightly runs against sun jdk1.4.2,
on xp. reopening as it seems like this issue was not fully fixed
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
Derby Info: [Patch Available, Existing Application Impact, Regression]
(was: [Existing Application Impact, Patch Available, Regression])
Reviewed and ran
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
Fix Version/s: 10.1.4.0
Derby Info: [Patch Available, Existing Application Impact, Regression]
(was: [Existing Application Impact, Regression,
autoincrement regression test fails with single diff - looks like just a
master issue
--
Key: DERBY-1719
URL: http://issues.apache.org/jira/browse/DERBY-1719
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
committed backport of change from trunk to 10.1:
r432414 | mikem | 2006-08-17
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali resolved DERBY-1681.
---
Resolution: Fixed
Regression (wrong results): Join predicate can be ignored for left-most child
in a chain of nested unions.
[ http://issues.apache.org/jira/browse/DERBY-1719?page=all ]
Mike Matrigali resolved DERBY-1719.
---
Fix Version/s: 10.1.3.2
Resolution: Fixed
Committed fix to 10.1 branch:
m101_142:61svn commit
Sending
predicatePushdown test gets queryplan diff, only on some platforms
--
Key: DERBY-1720
URL: http://issues.apache.org/jira/browse/DERBY-1720
Project: Derby
Issue Type: Bug
[ http://issues.apache.org/jira/browse/DERBY-1652?page=all ]
Mike Matrigali resolved DERBY-1652.
---
Resolution: Fixed
Update trigger updating the same rows as the original update does not throw
an exception ERROR 54038: Maximum depth of nested
[ http://issues.apache.org/jira/browse/DERBY-1713?page=all ]
Mike Matrigali updated DERBY-1713:
--
I admit I don't understand why there is much of a difference, during runtime
for those 2 queries. Do you have
any indexes on this data? From your ddl, derby
[ http://issues.apache.org/jira/browse/DERBY-1750?page=all ]
Mike Matrigali updated DERBY-1750:
--
Component/s: Regression Test Failure
Description:
encryption/encryption.fail:stress/stress.multi
* Diff file encryption/multi/stress.diff
***
[ http://issues.apache.org/jira/browse/DERBY-1694?page=all ]
Mike Matrigali updated DERBY-1694:
--
I see this test hang against ibm1.4.2, when running full suite against XP on a
laptop. Since switching I have tried 4 times and it has hung everytime. Looks
[ http://issues.apache.org/jira/browse/DERBY-1708?page=all ]
Mike Matrigali updated DERBY-1708:
--
it looks like this patch no longer applies as there have been subsequent
changes to the grantRevokeddl test, could you submit a new patch:
m3_142:131patch
[ http://issues.apache.org/jira/browse/DERBY-1708?page=all ]
Mike Matrigali updated DERBY-1708:
--
I am looking at building/testing this patch against the trunk, would appreciate
at least one other person to review.
Unprivileged user can perform lock
[ http://issues.apache.org/jira/browse/DERBY-1708?page=all ]
Mike Matrigali updated DERBY-1708:
--
Fix Version/s: 10.3.0.0
committed to trunk:
m1_142:148svn commit
Sendingjava\engine\org\apache\derby\impl\sql\compile\LockTableNode.java
Sending
[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ]
Mike Matrigali updated DERBY-1698:
--
committed patch to the trunk:
m3_142:172svn commit
Sending
java\testing\org\apache\derbyTesting\functionTests\master\SetQueryTimeoutTest.out
Sending
[ http://issues.apache.org/jira/browse/DERBY-1708?page=all ]
Mike Matrigali updated DERBY-1708:
--
Derby Info: (was: [Patch Available])
patch has been applied to trunk and 10.2, unchecking patch available.
Unprivileged user can perform lock table
[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ]
Mike Matrigali updated DERBY-1698:
--
back ported change from trunk to 10.2 branch:
m102_142:26svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ]
Mike Matrigali resolved DERBY-1698.
---
Resolution: Fixed
Derby Info: (was: [Patch Available])
fixes applied to trunk and 10.2 branch, unchecking patch available and
resolving.
Add
[ http://issues.apache.org/jira/browse/DERBY-1708?page=all ]
Mike Matrigali resolved DERBY-1708.
---
Resolution: Fixed
Unprivileged user can perform lock table statement on a table which he/she
does not have any access rights
[ http://issues.apache.org/jira/browse/DERBY-883?page=all ]
Mike Matrigali updated DERBY-883:
-
Affects Version/s: 10.2.1.0
This looks like a good thing to get into 10.2,.
Enhance GROUP BY clause to support expressions instead of just column
[ http://issues.apache.org/jira/browse/DERBY-1223?page=all ]
Mike Matrigali updated DERBY-1223:
--
Fix Version/s: 10.2.1.0
Update Getting Started to include instructions on setting JAVA_HOME variable.
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
Mike Matrigali updated DERBY-1659:
--
Fix Version/s: 10.2.1.0
Document describe and show tables functionality
---
Key: DERBY-1659
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
I will look at committing these test changes to trunk and 10.2
Regression (wrong results): Join predicate can be ignored for left-most child
in a chain of
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
committed d1681_test_v2.patch to trunk:
m1_142:27svn commit
Sending
java\testing\org\apache\derbyTesting\functionTests\master\predicatePushdown.out
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
backported and committed patch d1681_test_v2.patch from trunk to 10.2 branch:
r437487 | mikem | 2006-08-27 17:34:07 -0700 (Sun, 27 Aug 2006) | 14 lines
[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]
Mike Matrigali updated DERBY-1633:
--
Fix Version/s: 10.1.4.0
10.3.0.0
committed d1633_10_1_merge.patch to the 10.1 branch.
m101_142:48svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Mike Matrigali updated DERBY-1130:
--
Derby Info: [Patch Available, Existing Application Impact, Release Note
Needed] (was: [Patch Available, Release Note Needed, Existing Application
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Mike Matrigali updated DERBY-1130:
--
Derby Info: [Patch Available, Existing Application Impact, Release Note
Needed] (was: [Release Note Needed, Patch Available, Existing Application
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
merged test case from trunk to 10.1 branch:
437380
m101_142:9svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1681?page=all ]
Mike Matrigali updated DERBY-1681:
--
Fix Version/s: (was: 10.3.0.0)
Derby Info: [Patch Available, Existing Application Impact, Regression]
(was: [Regression, Existing Application
[ http://issues.apache.org/jira/browse/DERBY-1583?page=all ]
Mike Matrigali updated DERBY-1583:
--
Fix Version/s: 10.3.0.0
I ran a successful run of a full set of tests on XP, sun1.42 jvm. Committed
change to trunk.
m3_142:174svn commit
Sending
testSecMec in DerbyNetClient framework fails with FAIL: Server failed to
respond to ping - ending test
-
Key: DERBY-1793
URL:
Should create a test that verifies acceptable performance of network server
startup
---
Key: DERBY-1794
URL: http://issues.apache.org/jira/browse/DERBY-1794
Project:
[ http://issues.apache.org/jira/browse/DERBY-1793?page=all ]
Mike Matrigali updated DERBY-1793:
--
I went ahead and committed the longer max wait to the trunk. It is concerning
that the server startup is longer than 30 seconds, but seems reasonable to
1 - 100 of 2641 matches
Mail list logo
