id stringlengths 22 25 | commit_message stringlengths 137 6.96k | diffs listlengths 0 63 |
|---|---|---|
derby-DERBY-5121-6f271b4b | DERBY-1482/DERBY-5121
Rick Hillegas contributed a trigger test for DERBY-1482/DERBY-5121. With revision 1125453, that test was added to Changes10_8 but this test really is applicable for upgrades from all releases and should not be added into a specific version upgrade test. As a result, I am moving the test from Changes10_8.java to BasicSetup.java. This will ensure that the trigger test will get run for upgrades from all previous releases.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1130895 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5121-c1193bf7 | DERBY-5121 Data corruption when executing an UPDATE trigger
Committing changes to back out DERBY-1482 out of trunk(10.8 codeline). The changes have already been backed out of 10.7). In addition to engine code backport, it will also disable the tests that were added for DERBY-1482.
With DERBY-1482, these tests would not read in large object columns into memory because the triggers didn't need them. But now that DERBY-1482 changes are being backed out, the large object columns will be read in which can cause the test to run out of memory depending on how much heap is available to it. I will disable the tests from 10.7 too.
This commit also has a comment in DataDictionaryImpl:getTriggerActionString explaining the code changes for backout. I will add that comment in 10.7 too.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1084718 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
"\t\t// DERBY-1482 has caused a regression which is being worked",
"\t\t// under DERBY-5121. Until DERBY-5121 is fixed, we want",
"\t\t// Derby to create tri... |
derby-DERBY-5121-df731e99 | DERBY-5121 Data corruption when executing an UPDATE trigger
Changes made for DERBY-1482 caused corruption which is being worked
under DERBY-5121. The issue is that the generated trigger action
sql could be looking for columns (by positions, not names) in
incorrect positions. With DERBY-1482, trigger assumed that the
runtime resultset that they will get will only have trigger columns
and trigger action columns used through the REFERENCING column.
That is an incorrect assumption because the resultset could have
more columns if the triggering sql requires more columns. DERBY-1482
changes are in 10.7 and higher codelines. Because of this bug, the
changes for DERBY-1482 have been backed out from 10.7 and 10.8
codelines so they now match 10.6 and earlier releases. This in
other words means that the resultset presented to the trigger
will have all the columns from the trigger table and the trigger
action generated sql should look for the columns in the trigger
table by their absolution column position in the trigger table.
This disabling of code will make sure that all the future triggers
get created correctly. The existing triggers at the time of
upgrade (to the releases with DERBY-1482 backout changes in them)
will get marked invalid and when they fire next time around with
the release with DERBY-1482 changes backed out, the regenerated sql
for them will be generated again and they will start behaving
correctly. So, it is *highly* recommended that the users upgrade
from 10.7.1.1 to next point release of 10.7 or to 10.8
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1085613 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5133-8709c8a9 | DERBY-5133; nightly test failure in derbyall/storeall/storemore/SpaceTable
addressing review input; using JDBCTestCase.dropTable(), simplifying the retry and eliminating the code duplication, and adjusting comments.
Also addresses failure with Java8 because of different test case sequence.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1594451 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5139-84349af5 | DERBY-5101: TruncateTableTest depends on implicit ordering of test cases
Added a workaround for DERBY-5139 so that the test doesn't fail when testSelfReferencing runs first.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1082428 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-514-1ba0984d | DERBY-2242 ; remove metadata.java, metadata_test.java and odbc_metadata.java.
Test has been converted to junit test DatabaseMetaDataTest.
Also removed master file PhaseTester.out, orphaned from rev 407396 (DERBY-514)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@597464 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-514-5935349d | DERBY-514: get upgrade tests working with the test harness. Submitted
derby-514-patch3-v2.diff
Committed for Deepa Remesh <dremesh@gmail.com>
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@394157 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-514-6d02108f | DERBY-514: Enable upgrade tests to work with unpackaged classes. Add upgrade
tests to derbyall.
Committed for Deepa Remesh <dremesh@gmail.com>
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@407396 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-514-7095131a | DERBY-514 Integrate upgrade tests into test suite
Contributed by Deepa Remesh.
Attaching a patch 'derby-514-patch2-runtest-v1.diff' which enables the upgrade test to run with the test harness.
Summary:
* findCodeBase method in harness/jvm.java is changed to public. This method is used by upgrade test to get the location of new jar files.
* Adds the other derby jars to the jar file list in UpgradeTester. This will allow the test to run in client framework. I tried running the test in client framework and it looks like this will need new master file and some more work.
* In UpgradeTester, File.toURL method is used when creating class loader. This seems to be a better way to construct the URL.
* Master file update
This patch combined with the previous patch (derby-514-buildfiles-v1.diff) will allow the upgrade test to be run using RunTest. The location of old jars has to be passed in as a property in jvmflags. Command to run:
java -Djvmflags=-DderbyTesting.oldJarLocation=<location of 10.1 jars> org.apache.derbyTesting.functionTests.harness.RunTest upgradeTests/Upgrade_10_1_10_2.java
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@391844 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5141-a5357587 | DERBY-5141 SSLTest fails with java.net.SocketException: Default SSL
context init failed: null
Add some verbosity to NetworkServerTestSetup to show the server start
command with -Dderby.tests.debug=true. This does not fix the issue.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1085078 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/NetworkServerTestSetup.java",
"hunks": [
{
"added": [
"import org.apache.derbyTesting.junit.BaseTestCase;"
],
"header": "@@ -33,6 +33,7 @@ import java.security.PrivilegedExceptionAction;",
"removed": []
... |
derby-DERBY-5143-c85d4650 | DERBY-5143: Remove unnecessary copying of the map in getTypeMap()
- made the JDBC 4.0 overrides of getTypeMap() just call
super.getTypeMap(), and added SuppressWarnings annotation to silence
the unchecked conversion warnings in the overridden methods
- made the client implementation return EMPTY_MAP (immutable) instead
of an empty HashMap (mutable), to match the embedded implementation
- updated ConnectionTest to expect the returned map to be immutable
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1083917 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Connection.java",
"hunks": [
{
"added": [
"import java.util.Collections;"
],
"header": "@@ -26,6 +26,7 @@ import org.apache.derby.jdbc.ClientDataSource;",
"removed": []
}
]
},
{
"file": "java/... |
derby-DERBY-5145-87baa305 | DERBY-5145: Provide option to limit compatibility test to combinations that include trunk
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1132648 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-515-cd5e376d | DERBY-515 Network Server should log server start and shutdown time to derby.log
Patch contributed by Deepa Remesh.
Summary of patch:
* Removes identical master files in DerbyNetClient and DerbyNet for
derbynet/NSinSameJVM.java and moves it the top master directory.
* Modified tools/release/build.xml to point to the new master file.
* Adds comments as to why CheapDateFormatter and GMT is used to format
timestamp. Moves formatting of timestamp to a method getFormattedTimestamp().
This will be helpful if timestamp is planned to be used for more messages
as Kathey indicated.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@380722 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"\t\t",
"\t\t\t\t\tgetFormattedTimestamp()});"
],
"header": "@@ -561,10 +561,10 @@ public final class NetworkServerControlImpl {",
"removed": [
... |
derby-DERBY-5152-4e72f55c | DERBY-5152 Shutting down db, information that the thread received an interrupt will not be restored to thread's interrupt flag
Patch derby-5152-b. When a thread receives an interrupt Derby detects
this, it will reset the thread's flag and save the fact in its lcc
(LanguageConnectionContext), if available. If not (e.g. during boot)
it will save the information in a thread local variable. For
performance reasons, we use the lcc when available. However, when
shutting down the database, the lcc goes away, and when the JDBC call
returns to the application, the thread's interrupt flag will not be
reinstated as per our specification. This is because the lcc dies
before we do the restoring (under shutdown). So, the information that
the thread was interrupted is lost with the lcc going away.
This patch copies the information from lcc over to the thread local
variable when lcc is popped and adds a new test case to
InterruptResilienceTest.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1086443 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.InterruptStatus;"
],
"header": "@@ -75,6 +75,7 @@ import org.apache.derby.iapi.sql.ParameterValueSet;",
"re... |
derby-DERBY-5153-a899bbc8 | DERBY-5153: Intermittent ASSERT FAILED Internal Error-- statistics not found in selectivityForConglomerate when running InterruptResilienceTest
Removed the failing asserts and enabled the test case that exercises the code.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1088495 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/dictionary/TableDescriptor.java",
"hunks": [
{
"added": [
" * However, no locks are held to prevent the statistics from being dropped,",
" * so the method also handles the case of missing statistics by using a",
... |
derby-DERBY-5153-ae1478de | DERBY-5153: Intermittent ASSERT FAILED Internal Error-- statistics not found in selectivityForConglomerate when running InterruptResilienceTest
Added regression test case that reproduces the bug. Disabled for now.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1087636 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5157-42114dab | DERBY-5280: Large batch of DDL in a database procedure dies on a transaction severity error
Backed out the fix for DERBY-5161 since it's causing a regression and
shouldn't be needed after DERBY-5157.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1138787 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5157-cac43eee | DERBY-5157: Incomplete quoting of SQL identifiers in AlterTableConstantAction
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1086526 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/AlterTableConstantAction.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.StringUtil;"
],
"header": "@@ -84,6 +84,7 @@ import org.apache.derby.iapi.types.DataTypeDescriptor;",
"removed":... |
derby-DERBY-5158-86226a22 | DERBY-5158 Incomprehensible error message on client if attempting rollback after database has been shut down.
Scenario: app code calling client JDBC connection commit or rollback
after the database has been shut down. In the commit case the issue
and fix only applies if a transaction has been started, since
otherwise the client optimizes the commit away.
Patch DERBY-5158b, which corrects the protocol code on the client side
to cater for ENDUOWRM even in the error case (as sent by the
server). Looking at the DRDA standard, I managed to satisfy myself
that this is the correct behavior: section 7.5 Commit/Rollback
processing, where CR2 says:
"Application servers using remote unit of work protocols and
application servers using distributed unit of work but not protected
by a sync point manager must inform the application requester when the
current unit of work at the application server ends as a result of a
commit or rollback request by an application or application requester
request. This information is returned in the RPYDSS, containing the
ENDUOWRM reply message."
The "remote unit of work" is definitely ended, so...
Note that the (new) error stack trace is still different than with the
embedded driver, since there the 08003 will be directly reported as
the error (not wrapped in 06006 as shown below for the client side).
With this new code, on the client side, one can clearly see from the
exception stack that the underlying cause of the error is 08003. "No
current connection".
I added a new test, Derby5158Test.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1089795 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetConnectionReply.java",
"hunks": [
{
"added": [
" parseENDUOWRM(connection);",
" peekCP = parseTypdefsOrMgrlvlovrs();",
" if (peekCP == CodePoint.SQLCARD) {",
" NetSqlca... |
derby-DERBY-5159-00306c2e | DERBY-5159: ParameterMetaDataJdbc30Test fails with "'PMDD' is not recognized as a function or procedure"
Create shared procedure in the decorator so that the test cases
that need it can find it regardless of the order of execution.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1086559 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5161-42114dab | DERBY-5280: Large batch of DDL in a database procedure dies on a transaction severity error
Backed out the fix for DERBY-5161 since it's causing a regression and
shouldn't be needed after DERBY-5157.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1138787 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5165-dc57c1f4 | DERBY-5165; Prepared XA transaction locks are not kept across DB restart
Adding License comment to the test
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1624105 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5168-98ec83ef | DERBY-5168: Wrong syntax in identifier chain returned by SynonymAliasInfo.toString()
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1087641 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/types/SynonymAliasInfo.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.IdUtil;"
],
"header": "@@ -23,6 +23,7 @@ package org.apache.derby.catalog.types;",
"removed": []
}
]
}
] |
derby-DERBY-517-3a3105b7 | DERBY-517 ResultSet - relative(int rows) behaves different in embedded and client/server mode when the positioning before the first row or after the last row.
Submitted by Fernanda.Pizzorno@Sun.COM
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@348192 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ResultSet.java",
"hunks": [
{
"added": [
" ",
" // Keep maxRows in the ResultSet, so that changes to maxRow in the statement",
" // do not affect the resultSet after it has been created",
" pr... |
derby-DERBY-5170-11468253 | DERBY-5170: Client doesn't handle double quotes in savepoint names
Moved helper method that quoted SQL identifiers from ResultSet to a utility class, and made Connection use that method to quote savepoint names.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1088500 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Connection.java",
"hunks": [
{
"added": [
" stmt.executeX(",
" \"SAVEPOINT \" + Utils.quoteSqlIdentifier(savepointName) +",
" \" ON ROLLBACK RETAIN CURSORS\");"
... |
derby-DERBY-5172-6e591dc9 | DERBY-5172: testTimeAndDateWithCalendar (jdbcapi.CallableTest) fails intermittently with AssertionFailedError: hour expected: differs from actual.
Make the test convert between timezones via the local timezone, like
Derby does when passing a timestamp through a stored procedure.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1463874 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5173-3c7c7402 | DERBY-5173: RAFContainer.privGetRandomAccessFile() unwraps wrong exception type
Made run() wrap IOExceptions in StandardExceptions to prevent ClassCastException in the error handler.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1088491 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer.java",
"hunks": [
{
"added": [
"import java.io.FileNotFoundException;"
],
"header": "@@ -54,6 +54,7 @@ import java.util.Vector;",
"removed": []
},
{
"added": [
... |
derby-DERBY-5185-1cfe34ee | DERBY-5185 store/rollForwardRecovery.sql stuck in RAFContainer4.recoverContainerAfterInterrupt() during shutdown
Patch derby-5185-2b which fixes state a state maintenance bugs (in
threadDoingRestore/restoreChannelInProgress) maintenance when throwing
FILE_IO_INTERRUPTED. The first fixes the immediate problem.
It also adds a maximum number of retries for the readPage code and
fixes some cases whereby the state variable "threadsInPageIO" could
risk not being properly update when exceptions would get thrown. The
latter may be the underlying reason for what we see here.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1094572 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer4.java",
"hunks": [
{
"added": [
" // then. Otherwise protected by channelCleanupMonitor. Debugging value not",
" // safe on 1.4, but who cares.."
],
"header": "@@ -87,7 +87,8 @@ c... |
derby-DERBY-5185-4afad93f | DERBY-5185 store/rollForwardRecovery.sql stuck in RAFContainer4.recoverContainerAfterInterrupt() during shutdown
Patch derby-5185-1a.diff. Avoid waiting forever in the loop in
recoverContainerAfterInterrupt where we wait for other concurrent
threads to hit the wall (having seen ClosedChannelException), i.e. so
we know they waiting for this thread to clean up. The counting logic
(threadsInPageIO) here needs to be correct, if there is an error, we
could risk waiting forever, as seen in this issue.
This patch should be followed up by a patch to correct the logic, but
until such time, this patch improves on the situation.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1091221 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer4.java",
"hunks": [
{
"added": [
" // (ClosedChannelException) and are a ready waiting for us to clean up,",
" // so we can set them loose when we're done.",
" int retries... |
derby-DERBY-5185-a768c94c | DERBY-5185 store/rollForwardRecovery.sql stuck in RAFContainer4.recoverContainerAfterInterrupt() during shutdown
Follow-up patch derby-5185-3a which contains safe guard limits to two loops waiting for
a condition variable: wait maximum one minute to avoid infinite hangs.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1094728 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer4.java",
"hunks": [
{
"added": [
" int retries = MAX_INTERRUPT_RETRIES;",
""
],
"header": "@@ -308,6 +308,8 @@ class RAFContainer4 extends RAFContainer {",
"remove... |
derby-DERBY-5189-589b21f0 | DERBY-5189: PropertySetter should ignore GCJ installations
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1092333 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyPreBuild/PropertySetter.java",
"hunks": [
{
"added": [
" // Search the versions backwards (highest first) until a usable one",
" // is found.",
" for (int i = count - 1; i >= 0; i--) {",
" ... |
derby-DERBY-5196-586ae9de | DERBY-5196; Correct the layout of log.ctrl as described on the Derby web site
fixing the header in the source file
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1550525 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/log/LogToFile.java",
"hunks": [
{
"added": [
"\t\t (logfile counter, position)",
"\t\tint Derby major version",
"\t\tint Derby minor version",
"\t\tint subversion revision/build number",
... |
derby-DERBY-5210-f6e1e6f9 | DERBY-5210: Use java.nio.ByteBuffer in client.net.Request
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1102730 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/SignedBinary.java",
"hunks": [
{
"added": [],
"header": "@@ -25,9 +25,6 @@ public class SignedBinary {",
"removed": [
" /** Maximum value that cen be encoded by 6 bytes (signed). */",
" public static fi... |
derby-DERBY-5213-898c8da7 | DERBY-5213; Write tests to verify the interaction of TRUNCATE TABLE and online backup
- add a third fixture, which tests an uncommitted truncate table followed by freeze/copy/unfreeze
- remove the decorateSQL method and moves the creation and population of the truncable table to setUp(), and drops the table in teardown()
- reinstate the test in lang._Suite
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1383677 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5222-c4521269 | DERBY-5222: Compatibility tests fail to delete database directory
Wait for all forked processes to complete before testing the next combination.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1103742 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5222-e411e977 | DERBY-5222: Compatibility tests fail to delete database directory
Use BaseTestCase.removeDirectory() to delete the database directory so
that we get more details in the log when something goes wrong.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1101059 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5223-a00a0313 | DERBY-5223 Thread's interrupted flag not always preserved after Derby returns from JDBC API call
Patch DERBY-5223b: This fix moves the initialization of the variable
"interruptedException" earlier in
GenericLanguageConnectionContext#initialize and adds a missing
reinitialization to resetFromPool as a precaution (if
interruptedException is still non-null the connection should have
throws 08000).
The patch also changes the InterruptResilienceTest so that JUnit
asserts in the worker threads will get propagated to the main test
thread on completion, so any future errors in these invariants do not
get overlooked.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1102826 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java",
"hunks": [
{
"added": [
" interruptedException = null;"
],
"header": "@@ -377,6 +377,7 @@ public class GenericLanguageConnectionContext",
"removed": []
}... |
derby-DERBY-5224-7af858da | DERBY-5224: reduce cohesion by removing overzealous casting
Contributed by Dave Brosius <dbrosius@apache.org>.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1102679 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/locks/LockTableVTI.java",
"hunks": [
{
"added": [
"\t\t\t\tlock = (Latch) grantedList.next();"
],
"header": "@@ -100,10 +100,9 @@ class LockTableVTI implements Enumeration",
"removed": [
"//System... |
derby-DERBY-5232-0dfad316 | DERBY-5232 (Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there)
Adding a test case for default database creation with the checks for the existence of the 3 readme files. These readmes warn users against editing/deleting any of the files in the database directories. The location of the readme files are
1)at the db level directory,
2)in seg0 directory and
3)in the log directocy.
All the three readme files are named README_DONT_TOUCH_FILES.txt
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1409100 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5232-1bb2c59c | DERBY-5232 (Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there)
This commit fixes
a)a typo in the readme file content.
b)uses OutputStreamWrtier to deal with UTF-8 encoding for the readme files.
c)fixes the if condition used to create readme files
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1407170 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/RawStore.java",
"hunks": [
{
"added": [
"import java.io.OutputStream;"
],
"header": "@@ -75,7 +75,7 @@ import java.io.Serializable;",
"removed": [
""
]
},
{
"added": [... |
derby-DERBY-5232-393f243f | DERBY-5232 (Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there)
The earlier commit caused test failures because readme file creation was not getting done inside a privileged block. This commit fixes that problem and it was also fixes so typo and gets rid of redundant file close since that is already happening in the finally block.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1403807 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/RawStore.java",
"hunks": [
{
"added": [
" private String activePerms;"
],
"header": "@@ -149,6 +149,7 @@ public final class RawStore implements RawStoreFactory, ModuleControl, ModuleSup",
"removed": []
... |
derby-DERBY-5232-651c99e8 | DERBY-5232 (Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there)
This will create 3 readme(README_DONT_TOUCH_FILES.txt) files at database creation time, One at the database level, one in the "log" directory and another in the "seg0" directory.
a)Content of the readme file at the database level are as follows
# *************************************************************************
# *** Do not touch files in this directory! ***
# *** FILES IN THIS DIRECTORY AND SUB-DIRECTORIES CONSTITUES DERBY ***
# *** DATABASE WHICH INCLUDES THE DATA(USER AND SYSTEM) AND THE ***
# *** NECESSARY FILES FOR DATABASE RECOVERY. ***
# *** EDITING, ADDITING OR DELETING ANY OF THESE FILES MAY CAUSE DATA ***
# *** CORRUPTION AND LEAVE THE DATABASE IN NON-RECOVERABLE STATE. ***
# *************************************************************************
b)Content of the readme file at "seg0" directory are as follows
# *************************************************************************
# *** Do not touch files in this directory! ***
# *** FILES IN THIS DIRECTORY ARE USED BY THE DERBY DATABASE TO STORE ***
# *** USER AND SYSTEM DATA. EDITING, ADDING, OR DELETING FILES IN THIS ***
# *** DIRECTORY WILL CORRUPT THE ASSOCIATED DERBY DATABASE, AND WILL ***
# *** NOT BE RECOVERABLE. ***
# *************************************************************************
c)Content of the readme file at "log" directory are as follows
# *************************************************************************
# *** Do not touch files in this directory! ***
# *** FILES IN THIS DIRECTORY ARE USED BY THE DERBY DATABASE RECOVERY ***
# *** SYSTEM. EDITING, ADDING OR DELETING FILES IN THIS DIRECTORY WILL ***
# *** CAUSE THE DERBY RECOVERY SYSTEM TO FAIL LEADING TO UNRECOVERABLE ***
# *** CORRUPT DATABASES. ***
# *************************************************************************
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1403611 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/monitor/PersistentService.java",
"hunks": [
{
"added": [
" /**",
" The readme file cautioning users against touching the files in",
" the database directory ",
" */",
" ... |
derby-DERBY-5232-ce0c0aed | DERBY-5232 (Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there)
Remove redundant file length check on readme files. It is sufficient to check that they exist. Additionally, assert the value returned by file exists method.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1409254 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5233-6e61723e | DERBY-5233 Interrupt of create table or index (i.e. a container) will throw XSDF1 under NIO - connection survives
Patch DERBY-5233-2: The patch makes RAFContainer, when seeing an
interrupt exception during container creation, close it down and try
again, up to MAX_INTERRUPT_RETRIES times. Since RAFContainer should
work also under CDC/Foundation 1.1, the exceptions are checked using
reflection (NIO classes are excluded there).
I also adds a new test case to InterruptResilienceTest:
testCreateDropInterrupted.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1129764 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5234-355ebf60 | DERBY-5234: Add edge case tests for compression-related data corruption.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1335677 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5236-52660564 | DERBY-5236: Client driver silently truncates strings that exceed 32KB
Test case for the bug. Currently disabled.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1104365 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5236-7aa76512 | DERBY-5236: Client driver silently truncates strings that exceed 32KB
Prepare the network client for the possibility that a column is split
over more than two blocks in the response. This cannot happen until a
fix that makes the server stop sending truncated strings, has been
checked in.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1163131 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetCursor.java",
"hunks": [
{
"added": [
" checkForSplitRowAndComplete(4);"
],
"header": "@@ -413,18 +413,7 @@ public class NetCursor extends org.apache.derby.client.am.Cursor {",
"removed": [
... |
derby-DERBY-5236-9b3e218c | DERBY-5236: Client driver silently truncates strings that exceed 32KB
Disable the fix when talking to old clients because they may get a
StringIndexOutOfBoundsException if they receive longer strings, and
they also don't know exactly how to handle java.sql.DataTruncation
warnings.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1167470 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DDMWriter.java",
"hunks": [
{
"added": [
" // Find out how long strings the client supports, and possibly",
" // truncate the string before sending it.",
"",
" int maxByteLength = MAX_V... |
derby-DERBY-5236-b8501198 | DERBY-5236: Client driver silently truncates strings that exceed 32KB
Add a java.sql.DataTruncation warning to the result if a string was
truncated.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1167017 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/SqlException.java",
"hunks": [
{
"added": [],
"header": "@@ -22,7 +22,6 @@",
"removed": [
"import java.util.TreeMap;"
]
}
]
},
{
"file": "java/client/org/apache/derby/client/am/Sqlca.java",
... |
derby-DERBY-5236-c6e42941 | DERBY-5236: Client driver silently truncates strings that exceed 32KB
Truncate the strings at 65535 bytes instead of 32700 bytes, and make sure
that the truncation happens on a character boundary.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1164495 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DDMWriter.java",
"hunks": [
{
"added": [
" /**",
" * The maximum length in bytes for strings sent by {@code writeLDString()},",
" * which is the maximum unsigned integer value that fits in two bytes.",
... |
derby-DERBY-5238-902725f1 | DERBY-5238 VARCHAR size typos in some documentation topics
Modified comments in three Java source files.
Patches: DERBY-5238-2.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1125447 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/SystemProcedures.java",
"hunks": [
{
"added": [
"\t * IN INSERTCOLUMNLIST VARCHAR(32672), IN COLUMNINDEXES VARCHAR(32672),",
"\t * IN FILENAME VARCHAR(32672), IN COLUMNDELIMITER CHAR(1), "... |
derby-DERBY-5240-9ef6c29f | DERBY-5240 (Log Operating system information to derby.log on boot)
Adding following piece of information into derby.log for OS right after the existing info about JVM
OS name=XXX
OS architecture=YYY
OS version=ZZZ
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1371041 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/BaseDataFileFactory.java",
"hunks": [
{
"added": [
"\tprivate String osInfo;",
"\t"
],
"header": "@@ -135,6 +135,8 @@ public class BaseDataFileFactory",
"removed": []
},
... |
derby-DERBY-5244-be3da0b3 | DERBY-5244 DERBY-5244 DatabaseMetaData.getColumns(null, null, tableName, null) does not return the columns meta for a SYNONYM. This is because for
Adding test case for views. The test comments for table, views and synonym is as follows
* DERBY-5244 DatabaseMetaData.getColumns(null, null, tableName, null)
* does not return the columns meta for a SYNONYM. This is because for
* synonyms, we do not add any rows in SYSCOLUMNS. But the metadata query
* for DatabaseMetaData.getColumns() looks at SYSCOLUMNS to get the
* resultset. Views and Tables do not have problems because we do keep
* their columns information in SYSCOLUMNS.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1201945 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5244-be72b144 | DERBY-5244 DatabaseMetaData.getColumns(null, null, tableName, null) does not return the columns meta for a SYNONYM
Adding a test case which confirms the behavior noticed by DERBY-5244.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1199096 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5246-6d90df09 | DERBY-5246: Simplify bytecode generation for concatenation operator
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1127886 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/BinaryOperatorNode.java",
"hunks": [
{
"added": [],
"header": "@@ -600,9 +600,6 @@ public class BinaryOperatorNode extends OperatorNode",
"removed": [
"\t\t\t//following method is special code for concatenation ... |
derby-DERBY-5248-45b5ae15 | DERBY-5258
Fixing row level btree postcommit reclaim space to hold latch until end
of the internal transaction. Before this fix there was a very small window
(a few instructions) between the release of the latch and the commit of the
transaction where another transaction could access the page, insert rows,
and if a crash happens cause the undo of the purges of the reclaim space work
to fail.
It is proposed that this is what caused DERBY-5248, but without a repro it
can't be proved.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1132711 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreePostCommit.java",
"hunks": [
{
"added": [
" TransactionManager internal_xact = tc.getInternalTransaction();"
],
"header": "@@ -207,7 +207,7 @@ class BTreePostCommit implements Serviceable",
... |
derby-DERBY-5249-8d26b674 | DERBY-5249 A table created with 10.0.2.1 with constraints cannot be dropped with 10.5 due to NullPointerException with insane build or ASSERT FAILED Failed to find sharable conglomerate descriptor for index conglomerate with sane build
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1131272 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5249-94d3c58f | DERBY-5249 A table created with 10.0.2.1 with constraints cannot be dropped with 10.5 due to NullPointerException with insane build or ASSERT FAILED Failed to find sharable conglomerate descriptor for index conglomerate with sane build
Add a test for this issue. The test xtestDropTableAfterUpgradeWithConstraint()
is not currently enabled because the issue is not yet fixed.
Remove the x to enable the test once the issue is fixed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1130632 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-525-1022f8fc | DERBY-525 - getAsciiStreamshould replace non-ASCII characters with 0x3f, '?' to match embedded - Patch by Tomohito Nakayama (tomonaka@basil.ocn.ne.jp)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@292414 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ResultSet.java",
"hunks": [
{
"added": [
"\t\t",
"\t\tresult = new java.io.ByteArrayInputStream",
"\t\t\t(convertToAsciiByteArray((String) agent_.crossConverters_.setObject(java.sql.Types.CHAR,",
"\t\t\t\... |
derby-DERBY-525-8ecffdda | - DERBY-525_3 getAsciiStreamshould replace non-ASCII characters with 0x3f, '?' to match embedded - Patch by Tomohito Nakayama (tomonaka@basil.ocn.ne.jp)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@329372 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/AsciiStream.java",
"hunks": [
{
"added": [
"import java.io.StringReader;",
"",
"\t",
"\tpublic AsciiStream(String materializedString){",
"\t\tthis(materializedString,new StringReader(materialize... |
derby-DERBY-5252-f1512cdd | DERBY-5252: make GrantRevokeTest pass in non-English locale
This patch was contributed by Houx Zhang (houxzhang at gmail dot com)
This change adjusts 4 places in the test to compare the actual
error message text only if the test is running in the English locale.
This enables the test to pass when run in non-English locales, while
also preserving the error message text validation for runs of the
test in the English locale.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1134139 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5254-ab49fa3c | DERBY-5254: Unreserve the keywords which were added as part of implementing sequences.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1130127 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5256-67790a0e | DERBY-5256: Improve error reporting in common.sanity.AssertFailure
Added more specific error reporting, and fixed code that could result
in an NPE under some circumstances.
Patch file: derby-5256-1a-error_reporting.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1130964 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/shared/org/apache/derby/shared/common/sanity/AssertFailure.java",
"hunks": [
{
"added": [
" /**",
" * Tells if generating a thread dump is supported in the running JVM.",
" */",
" private boolean supportsThreadDump() {",
... |
derby-DERBY-5258-45b5ae15 | DERBY-5258
Fixing row level btree postcommit reclaim space to hold latch until end
of the internal transaction. Before this fix there was a very small window
(a few instructions) between the release of the latch and the commit of the
transaction where another transaction could access the page, insert rows,
and if a crash happens cause the undo of the purges of the reclaim space work
to fail.
It is proposed that this is what caused DERBY-5248, but without a repro it
can't be proved.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1132711 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreePostCommit.java",
"hunks": [
{
"added": [
" TransactionManager internal_xact = tc.getInternalTransaction();"
],
"header": "@@ -207,7 +207,7 @@ class BTreePostCommit implements Serviceable",
... |
derby-DERBY-5260-5f5bc5fb | DERBY-5260 Remove unused "replace" argument to backup variant of StorageFactoryService#saveServiceProperties
The patch "saveServiceProperties-1" removes redundant code.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1133123 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java",
"hunks": [
{
"added": [
"",
" /**",
" * Save service.properties during backup",
" *",
" * @arg serviceName backup location of the service"... |
derby-DERBY-5263-ae72a308 | DERBY-6003: Create row templates outside of the generated code
Upgrade test fix in preparation for the actual fix for this issue.
Improve SYSCS_INVALIDATE_STORED_STATEMENTS by making it null out the
plans in SYS.SYSSTATEMENTS. Previously, it only marked them as invalid.
Use the improved SYSCS_INVALIDATE_STORED_STATEMENTS to work around
problems in the upgrade tests when downgrading to a version that suffers
from DERBY-4835 or DERBY-5289. Remove the old workarounds for DERBY-4835,
DERBY-5105, DERBY-5263 and DERBY-5289, as they are now handled by the
centralized workaround that uses SYSCS_INVALIDATE_STORED_STATEMENTS.
This change is needed because later patches for this issue will change
the format of many stored plans, so more of the test cases need to work
around the downgrade bugs in some old versions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1418296 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
" * @param recompile Whether to recompile or invalidate"
],
"header": "@@ -4429,6 +4429,7 @@ public final class\tDataDictionaryImpl",
"removed": []
... |
derby-DERBY-5267-e39eee71 | DERBY-5267: Shut down engine for old versions in upgrade tests to save memory
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1135432 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5269-f81766ad | DERBY-5269: Remove unused methods getSocketAndInputOutputStreams and checkAlternateServerHasEqualOrHigherProductLevel in NetConnection
Removed unused methods getSocketAndInputOutputStreams and
checkAlternateServerHasEqualOrHigherProductLevel.
Patch file: derby-5269-1a-remove_methods.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1135976 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetConnection.java",
"hunks": [
{
"added": [],
"header": "@@ -1628,54 +1628,6 @@ public class NetConnection extends org.apache.derby.client.am.Connection {",
"removed": [
" protected int getSocketAndInputOutputStre... |
derby-DERBY-5271-d954835a | DERBY-5271: Client may hang if the server crashes due to a java.lang.Error
Tries to ensure that if the network server crashes due to a condition
raising java.lang.Error, the client socket will be closed on the server
side. Note that even if one of the worker threads crashes, the network
server itself may remain operational. If the JVM process dies, the
sockets will be closed anyway.
Patch file: derby-5271-1a-inital_fix_proposal.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1158108 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DRDAConnThread.java",
"hunks": [
{
"added": [
" } catch (Error error) {",
" // Do as little as possible, but try to cut loose the client",
" // to avoid that it hangs in a soc... |
derby-DERBY-5274-e43e7e2d | DERBY-5274: getColumns() doesn't work with auto generated identity
columns that start with large numbers
Removed hard-coded maximum length for the start value and increment in
the meta-data query.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1136371 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5278-631e46c9 | DERBY-5278: AssertionFailedError in IndexSplitDeadlockTest.testBTreeForwardScan_fetchRows_resumeAfterWait_unique_split()
Made synchronization between threads more reliable with wait/notify instead of sleep.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1136844 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5280-42114dab | DERBY-5280: Large batch of DDL in a database procedure dies on a transaction severity error
Backed out the fix for DERBY-5161 since it's causing a regression and
shouldn't be needed after DERBY-5157.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1138787 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5283-4eea8755 | DERBY-5283: Crash / process termination during SYSCS_DISABLE_LOG_ARCHIVE_MODE can leave service.properties broken
Adds recover logic for service.properties. To be able to recover there must be
a backup file present. There are three different cases the logic can handle:
o corrupt original (no EOF token) and backup: use backup
o orignal and backup: delete backup
o backup only: rename to original
Patch file: derby-5283-1b-recover.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1188109 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java",
"hunks": [
{
"added": [
"import java.io.BufferedReader;",
"import java.io.FileReader;",
"import java.io.BufferedWriter;",
"import java.io.OutputStreamWriter;"
... |
derby-DERBY-5284-b1043a6a | DERBY-5284 A derby crash at exactly right time during a btree split can cause a corrupt db which can not be booted.
Fixed a problem during BTREE split. The first phase of btree split sees
if it can reclaim space from committed deleted rows. If it finds any
it purges these rows in a nested internal transaction. It needs to hold
the latch on the page until end of transaction, but did not. This allowed
a very small window of a few instructions where another insert could use
the space on the page and then a system crash could cause the purges to undo
but fail due to the insert.
The fix was to hold the latch and let commit release it.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1138275 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreeController.java",
"hunks": [
{
"added": [
"\t * @return true if at least one row was purged. If true, then the routine",
" * will leave the page latched, and the caller will release",
... |
derby-DERBY-5288-df02986b | DERBY-5288: running multiple suites.All concurrently should be possible
Wait for the threads that read stdout and stderr to finish before trying
to fetch the output from SpawnedProcess.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1138795 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/SpawnedProcess.java",
"hunks": [
{
"added": [
" private final StreamSaver errSaver;",
" private final StreamSaver outSaver;",
" public SpawnedProcess(Process javaProcess, String name) {",
" ... |
derby-DERBY-5289-0f64b702 | DERBY-5289 Unable to boot 10.5.1.1 database - fails during soft/hard upgrade process for a new version number while trying to drop jdbc metadata
Checking testcase for DERBY-5289. In trunk theDERBY-3870 fix contributed by Knut Anders Hatlen fixed the issue so no code change is needed. Just the portion of DERBY-3870 that is relevant to DERBY-5289 will be backported to the other branches.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1139449 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5289-ae72a308 | DERBY-6003: Create row templates outside of the generated code
Upgrade test fix in preparation for the actual fix for this issue.
Improve SYSCS_INVALIDATE_STORED_STATEMENTS by making it null out the
plans in SYS.SYSSTATEMENTS. Previously, it only marked them as invalid.
Use the improved SYSCS_INVALIDATE_STORED_STATEMENTS to work around
problems in the upgrade tests when downgrading to a version that suffers
from DERBY-4835 or DERBY-5289. Remove the old workarounds for DERBY-4835,
DERBY-5105, DERBY-5263 and DERBY-5289, as they are now handled by the
centralized workaround that uses SYSCS_INVALIDATE_STORED_STATEMENTS.
This change is needed because later patches for this issue will change
the format of many stored plans, so more of the test cases need to work
around the downgrade bugs in some old versions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1418296 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
" * @param recompile Whether to recompile or invalidate"
],
"header": "@@ -4429,6 +4429,7 @@ public final class\tDataDictionaryImpl",
"removed": []
... |
derby-DERBY-5292-7bfb37a8 | DERBY-5292 SQLAuthorisation and views
Patch derby5292d: For views, the premissions collection is disabled
from tables in the query from-list since it should run with definer's
rights. However, this disabling did not work for all cases. The way to
reach all the "from" tables has been changed to use a node visitor
instead, so as to be able to also reach tables inside subqueries and
inside explicit JOIN and set operations, cf the repro issues. An added
test case was added to GrantRevokeTest: testViewDefinersRights.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1142635 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromBaseTable.java",
"hunks": [
{
"added": [
"import java.util.Iterator;"
],
"header": "@@ -75,14 +75,12 @@ import org.apache.derby.iapi.store.access.TransactionController;",
"removed": [
"impo... |
derby-DERBY-5293-ccb1894d | DERBY-5293: Replace bubble sort in DataDictionaryImpl and CreateTriggerNode with Collections.sort()
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1141005 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
"import java.util.Collections;",
"import java.util.Comparator;"
],
"header": "@@ -155,6 +155,8 @@ import org.apache.derby.iapi.util.IdUtil;",
"... |
derby-DERBY-530-82d721fd | DERBY-530
ClientDriver ignores Properties object in connect(String url, Properties connectionProperties) method
Send both the properties specified in the info parameter and those specified in the url to the server in the RDBNAM. user and password attributes will be the exception. user and password will be sent via the standard DRDA mechanism and excluded from the attributes sent with RDBNAM whether specified with the url or info properties. As a result of the combination, the order of attributes sent to the server may be different than originally specified in the URL.
Also added additional driver tests and attrbute tests to checkDriver.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@289227 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/jdbc/ClientDriver.java",
"hunks": [
{
"added": [
"import java.util.Enumeration;",
"import java.util.Properties;",
""
],
"header": "@@ -20,6 +20,9 @@",
"removed": []
},
{
"added": [... |
derby-DERBY-5300-39837074 | DERBY-5300: Change derby.tests.trace to print the class as well as fixture name
Introduces the following changes to the output controlled by derby.tests.trace:
a) Print '(emb)' or '(net)' to show which driver/framework is being used.
b) Test class names are shortened if possible. The following prefixes are
stripped off:
o 'org.apache.derbyTesting.functionTests.tests.'
o 'org.apache.derbyTesting.'
Patch contributed by Jayaram Subramanian (rsjay1976 at gmail dot com).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1185330 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/Utilities.java",
"hunks": [
{
"added": [
"",
" /**",
" * Function to eliminate known package prefixes given a class full path",
" * ",
" * @param test",
" * ... |
derby-DERBY-5300-e7b124dd | DERBY-5300: Change derby.tests.trace to print the class as well as fixture name
Changed code to agree with Javadoc param comment ("mainString" -> "test").
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1185465 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/Utilities.java",
"hunks": [
{
"added": [
" public static String formatTestClassNames(String test) {",
" if (test.startsWith(COMMON_FUNCTIONTEST_PREFIX)) {",
" return test.substring(COMMON_F... |
derby-DERBY-5308-f30426b5 | DERBY-1903 Convert largedata/LobLimits.java to junit
DERBY-5308 Investigate if largeData/LobLimits.java can be run for client
Patch derby-1903_client_diff.txt enables client for largedata.LobLimitsLite. It disables the test cases that fail with client:
DERBY-5338 client gives wrong SQLState and protocol error inserting a 4GB clob. Should be 22003
DERBY-5341 : Client allows clob larger than column width to be inserted.
DERBY-5317 cannot use setCharacterStream with value from C/Blob.getCharacterStream
Also fixes the test to fail if we do not get an exception for negative test cases and fixes a javadoc warning.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1147335 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5310-29ba0c10 | DERBY-5310: PropertySetter prints warning when building with JDK 7
Make PropertySetter recognize "Oracle Corporation" in java.vendor.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1142591 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyPreBuild/PropertySetter.java",
"hunks": [
{
"added": [
" private static final String JDK_ORACLE = \"Oracle Corporation\";"
],
"header": "@@ -122,6 +122,7 @@ public class PropertySetter extends Task",
"removed": []
... |
derby-DERBY-5312-08b4ed59 | DERBY-5312 InterruptResilienceTest failed with ERROR 40XD1: Container was opened in read-only
Patch derby-5312-simplify-reopen-1. It fixes the race condition by
reducing the amount of work done under reopening the container, thus
side stepping the issue by no longer updating the state variable that
caused the race.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1148344 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer.java",
"hunks": [
{
"added": [
" private static final int REOPEN_CONTAINER_ACTION = 8;"
],
"header": "@@ -74,16 +74,8 @@ class RAFContainer extends FileContainer implements PrivilegedException... |
derby-DERBY-5313-e828232e | DERBY-5313: Assert failure with CASE expression in GROUP BY clause
Remove assert that doesn't expect expressions in the GROUP BY list.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1575866 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5316-09ecd71c | DERBY-5343: Upgrade tests failing with java.lang.IllegalAccessException
Rework the workaround for DERBY-23 added by DERBY-5316 so that it
doesn't attempt to modify final fields. Modifying final fields
doesn't seem to work prior to Java 5.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1148302 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5316-e9666094 | DERBY-5316: Unload old JDBC drivers when done with them in the upgrade tests
Added a workaround for DERBY-23.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1145973 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5316-eb60359d | DERBY-5316: Unload old JDBC drivers when done with them in the upgrade tests
Assert that the driver is only unloaded in the affected versions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1145553 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5316-f89c1b58 | DERBY-5316: Unload old JDBC drivers when done with them in the upgrade tests
When we're done with an old version in the upgrade test, deregister all
JDBC drivers in the old version's class loader from DriverManager.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1145111 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5317-b862050f | DERBY-5317: Detect attempts to reuse a connection that in the middle of sending a request to the server. Use this to provide a better error message and avoid the NPE.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1530704 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Agent.java",
"hunks": [
{
"added": [
" ",
" abstract public void beginWriteChainOutsideUOW() throws SqlException;"
],
"header": "@@ -267,9 +267,8 @@ public abstract class Agent {",
"removed": [
... |
derby-DERBY-5317-f30426b5 | DERBY-1903 Convert largedata/LobLimits.java to junit
DERBY-5308 Investigate if largeData/LobLimits.java can be run for client
Patch derby-1903_client_diff.txt enables client for largedata.LobLimitsLite. It disables the test cases that fail with client:
DERBY-5338 client gives wrong SQLState and protocol error inserting a 4GB clob. Should be 22003
DERBY-5341 : Client allows clob larger than column width to be inserted.
DERBY-5317 cannot use setCharacterStream with value from C/Blob.getCharacterStream
Also fixes the test to fail if we do not get an exception for negative test cases and fixes a javadoc warning.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1147335 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-5318-840ed3f5 | DERBY-5318: Use assertDirectoryDeleted in ReplicationRun and remove dead code
Use assertDirectoryDeleted to get better error reporting when the test fails
to delete a database directory.
Remove dead code in ReplicationRun and Utils.
Patch file: derby-5318-1a-cleanup.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1146644 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-532-00df88c3 | DERBY-532: Support deferrable constraints
Patch derby-532-testAlterConstraintInvalidation.
Adds a fixture to test that prepared statement is invalidated when a
table its depends on undergoes an ALTER TABLE ALTER CONSTRAINT
statement. As it turns out, this is already handled by the common
machinery for ALTER TABLE.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1519045 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-532-0493010b | DERBY-532 Support deferrable constraints
Substituted BaseJDBCTestCase#dropTable for home grown version, we
prefer the standard way to do it.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1594255 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-532-400cc602 | DERBY-532 Support deferrable constraints
Patch derby-532-nullableUniqueFix. When we changed the implementation from
special treatment of deferrable constraints in the BTree, a couple of extra
predicates needed to be added were omitted - added those here: we should not
mark the physical index with "uniqueWithDuplicateNulls" if it is deferrable.
This error was found when running the regressions with default deferrable for
all pk and unique constraints.
We also removed an unused flag "hasDeferrableChecking" in the same places (it is
not longer used by the physical index).
Added a new test case, testCompressTable, which tests the
"uniqueWithDuplicateNulls" case.
We also change the behavior in the following way for deferrable, but not
deferred constraints: if we hit a time-out or dead-lock when checking uniqueness
(in the BTree scan), we throw that time-out or dead-lock. Up till now we
converted it to a duplicate exception. We will only assume it can be a duplicate
- for later checking - iff the constraint mode is deferrable.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1550152 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/InsertResultSet.java",
"hunks": [
{
"added": [
"",
" if ( cd.getIndexDescriptor().isUniqueWithDuplicateNulls() &&",
" !cd.getIndexDescriptor().hasDeferrableChecking() )"
],
... |
derby-DERBY-532-51e62681 | DERBY-532 Support deferrable constraints
Patch derby-532-test-speedup changes ConstraintCharacteristicsTest to
use a main memory database for some tests for increased speed. It also
changes the way SystemPropertyTestSetup for static properties closes
down the database to not deregister the driver; without this change we
saw a test setup try to connect via the client driver to a Derby server
engine without a registered driver.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1550308 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/ConnectionPoolDataSourceConnector.java",
"hunks": [
{
"added": [
"import org.apache.derby.shared.common.sanity.SanityManager;"
],
"header": "@@ -29,6 +29,7 @@ import java.util.Properties;",
"removed": []
... |
derby-DERBY-532-831e54e7 | DERBY-532 Support deferrable constraints
Patch derby-532-allow-pk-unique-1, which opens up for using deferrable
constraints for primary key and unique constraints, i.e. it is no
longer required that the special property "derby.constraintsTesting"
be used for those constraints, since the implementation is complete
modulo bugs. Upgrade tests still remain to be built, though.
For foreign key and check constraints as well as for "not enforced",
the property will still required till the implementation for those is
completed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1555006 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/SetConstraintsConstantAction.java",
"hunks": [
{
"added": [],
"header": "@@ -104,13 +104,6 @@ class SetConstraintsConstantAction extends DDLConstantAction",
"removed": [
" // Remove when feature D... |
derby-DERBY-532-908f0a96 | DERBY-532 Support deferrable constraints
A patch ("derby-532-fix-metadata-1") that fixes broken database
metadata for deferred constraint indexes: the metadata query used the
method IndexDescriptor#isUnique to determine logical uniqueness, but
it really represents physical uniqueness now. For deferred unique
constraints, the method that should be used is
"isUniqueDeferrable". Added a test, and also added client/server run
of the regression test for deferred constraints.
Before the fix, the added test fixture "testDatabaseMetaData" failed
in that the index in question was identified as non unique, but it is
logically unique and so should be reported as such.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1550113 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-532-c4cfffbb | DERBY-532 Support deferrable constraints
Added an extra test case.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1577134 13f79535-47bb-0310-9956-ffa450edef68
| [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.