id stringlengths 22 25 | commit_message stringlengths 137 6.96k | diffs listlengths 0 63 |
|---|---|---|
derby-DERBY-4-2060c4a6 | DERBY-4397 Allow ORDER BY in subqueries
Patch derby-4397-2 which implements this functionality and also adds a
new test, OrderByInSubqueries. This patch also solves DERBY-4.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@891952 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/CreateViewNode.java",
"hunks": [
{
"added": [
"\tprivate OrderByList orderByList;"
],
"header": "@@ -68,7 +68,7 @@ public class CreateViewNode extends DDLStatementNode",
"removed": [
""
... |
derby-DERBY-400-66125641 | DERBY-400: Fixed the SQLState for some of the new client messages
to better match what is required by SQL2003
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@372240 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/shared/org/apache/derby/shared/common/reference/SQLState.java",
"hunks": [
{
"added": [
" String NOT_IMPLEMENTED = \"0A000.S\";",
" String JDBC2_METHOD_NOT_IMPLEMENTED = \"0A002.S\";"... |
derby-DERBY-400-e4b24389 | DERBY-400: Fixed the SQL states for warnings so they are compliant with
SQL2003 -- can't use SQL states that are reserved for standard
SQL States.
Also refactored the two messages for JDBC2 not supported and JDBC3
not supported into a single message.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@372368 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/CallableStatement.java",
"hunks": [
{
"added": [
" new MessageId(SQLState.JDBC_METHOD_NOT_IMPLEMENTED));"
],
"header": "@@ -915,7 +915,7 @@ public class CallableStatement extends PreparedStatemen... |
derby-DERBY-4001-7e23da13 | DERBY-4001: Sequence comparison with "ALL" does not yield correct results
There are three essential changes in the patch:
1) ProjectRestrictNode.pullOptPredicates()
Don't pull any predicates if the from table is marked as a not exists
table. This way the flattening of queries like the ones below will
work, because the predicate 1<>1 is not pulled out and applied on the
outer table.
SELECT * FROM T WHERE NOT EXISTS (SELECT * FROM T WHERE 1<>1)
SELECT * FROM T WHERE X < ALL (SELECT X FROM T WHERE 1<>1)
SELECT * FROM T WHERE X NOT IN (SELECT X FROM T WHERE 1<>1)
2) SubqueryNode.preprocess()
Don't allow not exists flattening unless all the predicates in the
subquery reference the base table of the inner query. When all the
predicates reference that table, none of them will be used in the
outer query, so they won't cause any trouble for the flattening. This
makes queries like the one below work:
SELECT * FROM T T1 WHERE NOT EXISTS (SELECT * FROM T T2 WHERE T1.X > 100)
No flattening will happen in this case, though.
Although it may sound like (2) would prevent the example queries in
(1) from being flattened, that's not the case. This is because simple
predicates like 1<>1 are pushed down before SubqueryNode.preprocess()
gets to the flattening, so it doesn't see those predicates. The
flattening is still safe, since we have made sure that those
predicates won't be pulled out again.
3) SubqueryNode.preprocess()
If an ALL subquery or a NOT IN subquery is flattened, a new join
condition is created, for instance
WHERE X < ALL (SELECT Y ...) results in the join condition X >= Y
and
WHERE X NOT IN (SELECT Y ...) results in the join condition X = Y
The patch adds a check so that the flattening only happens if the
right side of the join condition references the base table of the
subquery. If it does, we know that the join condition cannot be used
to filter rows from the outer table, so it's safe to do the
flattening. This prevents queries like the ones below from being
flattened, and they now work as expected:
SELECT * FROM T WHERE X < ALL (SELECT 100 FROM T)
SELECT * FROM T T1 WHERE X = ALL (SELECT T1.X FROM T)
SELECT * FROM T WHERE X NOT IN (SELECT 100 FROM T)
SELECT * FROM T T1 WHERE X NOT IN (SELECT T1.X+100 FROM T)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@769273 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/SubqueryNode.java",
"hunks": [
{
"added": [
"\t\t\treturn getNewJoinCondition(leftOperand, getRightOperand());"
],
"header": "@@ -668,10 +668,7 @@ public class SubqueryNode extends ValueNode",
"removed":... |
derby-DERBY-4018-c6fc81ea | DERBY-4018: ArrayIndexOutOfBoundsException in TopService.inService under heavy multithreaded use of EmbeddedDriver
Closed another unsynchronized window between Vector.size() and
Vector.elementAt().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@790218 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/monitor/TopService.java",
"hunks": [
{
"added": [
" // DERBY-4018: Need to hold the synchronization over the entire loop",
" // to prevent concurrent modifications from causing an",
" // Ar... |
derby-DERBY-4018-f0e75f3f | DERBY-4018: ArrayIndexOutOfBoundsException in TopService.inService under heavy multithreaded use of EmbeddedDriver
Factored out two for loops and surrounded them with synchronization on
the vector they were iterating over. This prevent others from changing
the size of the vector between the calls to Vector.size() and
Vector.get().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@789264 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/monitor/TopService.java",
"hunks": [
{
"added": [
" ModuleInstance module = findModuleInstance(instance);",
" if (module != null) {",
" topModule = module;",
" ... |
derby-DERBY-4027-8072a568 | DERBY-4027: An attempt was made to access an out of range slot on a page
When a new value is inserted into an index backing a nullable unique
constraint, a check is performed to verify that the adjacent slots do
not contain the same value as the one being inserted. This extra check
is needed because the index backing such a constraint is not unique
(it allows multiple NULL values).
If the spot on which the new value is inserted is at the beginning or
the end of the index page, the last value of the previous page or the
first value of the next page is checked. Currently, the code attempts
to read that value right after the slot pointer has been moved to that
page. This was the cause of the bug, as that page may be empty, and
any pointer to a slot on an empty page is pointing to a non-existent
slot, hence the out-of-range-slot error.
This patch fixes the bug by checking again after moving to another
page that we are attempting to read a valid row. If not, we skip to
the next (or previous, depending on the direction of the traversal)
index page in the chain and look for a duplicate there.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@744984 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreeController.java",
"hunks": [
{
"added": [
" // DERBY-4027: We have moved to the previous page and need",
" // to recheck that the slot number is valid (it won't be",
... |
derby-DERBY-4028-4d5163b2 | DERBY-4028: two rows can be inserted with the same value in a column that a unique constraint on that column should prevent
If the slot next to the one where a row is inserted contains a deleted
duplicate, move past it and see if there's another non-deleted
duplicate hidden behind it.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@752826 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreeController.java",
"hunks": [
{
"added": [
"",
" // If we found a deleted row, we don't know whether there",
" // is a duplicate, so we need to continue the search.",... |
derby-DERBY-4037-d43d4c3e | DERBY-4037
updated test to wait longer if expected background tasks have not cleaned up
expected pages yet. Fast machines should see no slowdown in the test. Slower
machines will wait up to 100 seconds before reporting failure after checking
iteratively for result every 1 second. Also enhanced printout to identify
which test is failing between the 2 possibilities.
/mikem
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@803694 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4038-1a363021 | DERBY-4038; convert access.sql to junit to avoid an intermittent error on IBM zseries machines when the test is run in the encryption suite.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@897938 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/suites/EncryptionSuite.java",
"hunks": [
{
"added": [
"import java.sql.Connection;",
"import java.sql.Statement;",
"import java.util.Properties;",
"import org.apache.derbyTesting.functionTests... |
derby-DERBY-404-00d8393f | DERBY-404 Remove buggy code from RowUtil.isRowEmpty and never used parameter and fix callers.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@293436 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/store/access/RowUtil.java",
"hunks": [
{
"added": [
"\t\tReturns true if row is null or row.length is zero.",
"\t\t@return true if row is empty.",
" DataValueDescriptor[] row) "
],
"header": "@@ -24... |
derby-DERBY-4040-a4a66c4b | DERBY-4040: SQLChar.getLength returns wrong length for some data values.
When asked to return the character length of a SQLChar or SQLVarchar and
the value is represented as a stream, skip the two header bytes and then
decode the whole stream. The cause of the bug being fixed, was that the
byte length was used as the character length.
Patch file: derby-4040-1a-SQLChar_length_and_test.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@742357 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/SQLChar.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.services.io.InputStreamUtil;"
],
"header": "@@ -44,6 +44,7 @@ import org.apache.derby.iapi.jdbc.CharacterStreamDescriptor;",
"removed": []
... |
derby-DERBY-4042-4e83499f | DERBY-4042: Removed double quote from file name used in test
The double quote caused failures on Windows.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@740698 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4042-ccc1b8d6 | DERBY-4042: org.apache.derby.impl.load.Import needs to escape single quotes
Made sure that the export and import procedures properly quoted string
literals and SQL identifiers when constructing internal SQL
statements. Achieved by using the helper methods in StringUtil and
IdUtil.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@739830 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/load/ExportResultSetForObject.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.IdUtil;"
],
"header": "@@ -27,6 +27,7 @@ import java.sql.ResultSet;",
"removed": []
}
]
},
{
"file": ... |
derby-DERBY-4044-c61e11be | DERBY-4044: Use helper methods from IdUtil to quote SQL identifiers in EmbedResultSet
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@890357 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/EmbedResultSet.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.IdUtil;"
],
"header": "@@ -79,6 +79,7 @@ import java.util.Calendar;",
"removed": []
},
{
"added": [
... |
derby-DERBY-4050-8f33dfd1 | DERBY-4050 Multithreaded clob update causes growth in table that does not get reclaimed
- Changes clob update case to call getPage() instead of getPageNoWait() so we are sure to reclaim the page.
- Adds some debug statements for other places that we might not reclaim space.
- Adds a test.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@743023 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/ReclaimSpaceHelper.java",
"hunks": [
{
"added": [
" {",
" }",
" {",
" // If code gets here, the space will be lost forever, and",
" ... |
derby-DERBY-4053-ad40edaf | DERBY-4053 The local XA connections were not getting rollback during Database close and
this resulted into exception at connection close if the connection object had any pending
transaction. Made changes so that all the connections(except global XA connections) will
have their transactions rolled back before those connections are closed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@793588 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/Database.java",
"hunks": [
{
"added": [],
"header": "@@ -70,7 +70,6 @@ class Database",
"removed": [
""
]
},
{
"added": [],
"header": "@@ -80,8 +79,6 @@ class Database",
"remov... |
derby-DERBY-4054-b514f88e | DERBY-4054 ClobReclamationTest.xtestMultiThreadedUpdateTableLocking() demonstrates the problem. This does not fix the issue.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@743820 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4055-921b2648 | DERBY-4059 If space reclamation cannot obtain container lock it will not retry getting the lock
This change does make the change so that the retry occurs but in practical application it is unlikely that we will get the lock after three retries, because the retry happens so quickly. See https://issues.apache.org/jira/browse/DERBY-4055?focusedCommentId=12673436#action_12673436 for suggestions on long term solutions to the retry problem.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@745982 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/ReclaimSpaceHelper.java",
"hunks": [
{
"added": [
"import org.apache.derby.shared.common.reference.SQLState;"
],
"header": "@@ -42,6 +42,7 @@ import org.apache.derby.iapi.store.raw.Transaction;",
"rem... |
derby-DERBY-4055-ad8fd168 | DERBY-4055 Test case to reproduce part of the issue pertaining to not getting the row lock. To reproduce enable ClobReclamationTest.xtestMultiThreadUpdateSingleRow(). This does not fix the issue.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@743867 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4057-1bd9cd27 | DERBY-4057 Space is not reclaimed if transaction is rolled back
a few changes to make the ClobReclamationTest better behaved across a variety
of platforms. The test tries to measure background thread behavior, and needs
to allow for machines/jvms that might be single threaded and slow.
In one case added a sleep after all aborts to allow the background thread
to catch up and mark all pages but head one free.
In other case added more to the fudge factor of how much immediate insert
might progress before background thread can catch up and make free page
available. If this does not work may just need to add sleep after every
insert.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1641526 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4057-2678c360 | DERBY-4057
Removing one check in test that is failing across platforms. Separate
work under DERBY-6775 will improve the test in this area.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1643463 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4057-2cd0cc18 | DERBY-4057 Space is not reclaimed if transaction is rolled back
Another change to try and get test to behave well across all platforms.
Still encountering some issues that I believe are because background work
piles up on slow machines.
Trying to address errors encountered in nightly tests:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1643981-suites.All_diff.txt
http://download.java.net/javadesktop/derby/request_5600553/javadb-task-3984530.html
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1644145 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4057-888d12ea | DERBY-4057 Space is not reclaimed if transaction is rolled back
Added infrastructure called at insert abort time to queue post abort work.
After the abort work is queued in the case of aborted inserts to reclaim
space and if possible mark pages free, which then in turn allows them to
be used by subsequent work on the table. This work queues this work
on heap tables when the aborted insert is the last row on a page, or
if the aborted insert is a row that contains a long column (a row that
is bigger than a page - usually a blob or clob), or a long row (a row
that spans multiple pages).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1641418 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/store/access/conglomerate/ConglomerateFactory.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.store.access.AccessFactory;",
"import org.apache.derby.iapi.store.raw.PageKey;"
],
"header": "@@ -27,9 +27... |
derby-DERBY-4057-dbde907f | DERBY-6774 org.apache.derbyTesting.functionTests.tests.lang.AlterTableTest.testAddIdentityColumn failed with assert in nightlys
Temporarily removing assert that is failing, looks like code should handle
the condition anyway. Will renable after figuring out what is going on,
hoping this will allow for clean runs from others while I work on this issue.
My current theory is that there is a long time problem with alter table
and the conglomerate cache that has been uncovered by this relatively new
test and the new background work introduced by DERBY-4057.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1641753 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/heap/Heap.java",
"hunks": [
{
"added": [
" // DERBY-6774 - temp disabling this ASSERT while working on",
" // why it is firing in trunk. The hope is that trunk tests",
" /... |
derby-DERBY-4057-f56c601d | DERBY-4057 Add disabled test case (xtestReclamationOnRollback() ) for the
issue that space is not reclaimed on rollback.This does not fix the issue
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@744169 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4060-aeb43258 | DERBY-4060: Blob.getBinaryStream(long,long) is off by one for the pos+len check.
Changed the pos/length checks to allow obtaining a stream reading the last
byte/char from the LOB.
The JavaDoc for Blob.getBinaryStream(long,long) and
Clob.getCharacterStream(long,long) (JDBC 4.0) incorrectly states that the
position plus the requested length of the stream cannot be larger than the
length of the LOB. Since positions in JDBC are 1-based, this makes it impossible
to read the last byte/char in the LOB. Derby adhered to the spec.
The changes to CharAlphabet/LoopingAlphabetReader were done to allow passing
an alphabet object around for constructing streams.
Patch file: derby-4060-1b-sub_stream_fix.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@749235 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Lob.java",
"hunks": [
{
"added": [
" * d) (pos -1) + length > (length of LOB)"
],
"header": "@@ -317,7 +317,7 @@ public abstract class Lob implements UnitOfWorkListener {",
"removed": [
" ... |
derby-DERBY-4061-28365b04 | DERBY-4061:InputStream returned from Blob.getBinaryStream(long, long) terminates the stream by returning 0, should return -1.
Fixed bug where calling code would enter infinite loop because 0 was returned instead of -1 (EOF). The problem occurred because the actual number of bytes to read was calculated and the case where zero bytes remained wasn't handled properly.
Patch file: derby-4061-1b.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@746236 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/UpdatableBlobStream.java",
"hunks": [
{
"added": [
" long remaining = maxPos - pos;",
" // Return EOF if the maximum allowed position has been reached,",
" // and we're trying to read at least ... |
derby-DERBY-4066-356155c5 | DERBY-4066: Add test cases for large (>1M) LOB inout args.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@984916 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4066-75a4806f | DERBY-4066: Allow LOBs as function/procedure input arguments and return values. LOBs still can't be used as output and inout arguments to procedures.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@982936 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/DataType.java",
"hunks": [
{
"added": [
"import java.sql.Blob;",
"import java.sql.Clob;"
],
"header": "@@ -34,6 +34,8 @@ import org.apache.derby.iapi.services.sanity.SanityManager;",
"removed": []
... |
derby-DERBY-4066-94df7fbd | DERBY-4066: Allow LOBs as OUT/INOUT procedure arguments.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@984393 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetCursor.java",
"hunks": [
{
"added": [
" if ( netResultSet_ != null ) { netResultSet_.markLOBAsPublished(column); }"
],
"header": "@@ -1083,7 +1083,7 @@ public class NetCursor extends org.apache.derby.cli... |
derby-DERBY-4067-b3bfe123 | DERBY-4067: ClientConnectionPoolDataSource.getPooledConnection and ClientXADataSource.getXAConnection ignore connection attributes
DERBY-2468: would be nice if traceFile=filename connection attribute would be supported with ClientConnectionPoolDataSource and ClientXADataSource
Made two changes:
- moved the parsing of the connection attribute string to before the log
writer is constructed, since the construction may depend on some attributes
specified in the connection attribute string
- added parsing of the connection attribute string to the client ConnectionPool
and XA data sources
Also re-enabled 'testClientMessageTextConnectionAttribute' and removed a
work-around for the issue fixed by this commit.
Patch file: derby-4067-1a-update_attrs.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@965793 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/jdbc/ClientConnectionPoolDataSource.java",
"hunks": [
{
"added": [
" updateDataSourceValues(",
" tokenizeAttributes(getConnectionAttributes(), null));"
],
"header": "@@ -74,6 +74,8 @@ publ... |
derby-DERBY-4071-c00561a1 | DERBY-4071 AssertFailure when selecting rows from a table with CHARACTER and VARCHAR columns
Patch derby-4071 which fixes this issue.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@754579 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/GroupByNode.java",
"hunks": [
{
"added": [
"\t * In the query rewrite for group by, add the columns on which we are doing",
"\t * the group by.",
"\t *",
"\t * @return havingRefsToSubstitute visito... |
derby-DERBY-4072-beac4f39 | DERBY-4072 Improve error message if log files are not writable.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@749410 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/log/LogToFile.java",
"hunks": [
{
"added": [
"\t\t\t\t\tIOException accessException = null;"
],
"header": "@@ -982,7 +982,7 @@ public final class LogToFile implements LogFactory, ModuleControl, ModuleSupport",
... |
derby-DERBY-4073-a7ab05c3 | DERBY-4073: Creation/configuration of ClientXDataSource fails because of two setSsl methods.
Removed the method setSsl(int).
Added constants for the valid values for setSsl(String).
Documented setSsl(String) and some other methods.
Patch file: derby-4073-1a-add_docs_and_remove_setSsl_int.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@753176 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/jdbc/ClientBaseDataSource.java",
"hunks": [
{
"added": [
" /** The constant indicating that SSL encryption won't be used. */",
" private final static String SSL_OFF_STR = \"off\";",
" /** The constant indicating tha... |
derby-DERBY-4079-69a192ae | DERBY-4079 Add support for SQL:2008 <result offset clause> and <fetch first clause> to limit result set cardinality
Added this new feature, corresponding to patch derby-4079-3. Documentation is committed separately.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@754558 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/CursorNode.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.types.DataValueDescriptor;"
],
"header": "@@ -34,6 +34,7 @@ import org.apache.derby.iapi.sql.dictionary.DataDictionary;",
"removed"... |
derby-DERBY-4081-4f376647 | DERBY-4081: BTreeController.comparePreviousRecord() may fail to release latch on left-most leaf
When a new value is inserted into a nullable unique index, the rows
immediately to the left and the right of the insertion point are
checked for duplicates. comparePreviousRecord() checks the rows to the
left of the insertion point. If the row immediately to the left is
marked as deleted, it will have to go further to the left until it
finds a row that is not deleted.
Now this check may cross page boundaries, and if it does so, and all
the rows to the left of the insertion point are deleted,
comparePreviousRecord() will return NO_MATCH before the latch
left-most leaf in the index has been released.
This means that the left-most leaf is still latched when
comparePreviousRecord() returns, which it is not supposed to be unless
the new value was actually inserted into the left-most leaf. The
unexpected extra latch may cause deadlocks or livelocks.
This patch adds a test that runs into a livelock because of the bug,
and it fixes the bug by releasing the latch on the left-most leaf
before returning NO_MATCH from comparePreviousRecord().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@805696 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4083-571f201a | DERBY-4083: BTreeScan.delete() throws AM_RECORD_NOT_FOUND if record is found
Changed the logic so that the exception is thrown if the record is not found.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@952131 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/unitTests/store/T_b2i.java",
"hunks": [
{
"added": [
"\t\t\t\tt_020(tc) &&",
"\t\t\t\tt_021(tc)"
],
"header": "@@ -173,7 +173,8 @@ public class T_b2i extends T_MultiIterations",
"removed": [
... |
derby-DERBY-4087-14fde85b | DERBY-4087 Clean up debug printing of the abstract syntax trees after parsing, binding and optimization
Reverting use of class Patter as it is not available in Foundation
1.2, so it cannot be sued in engine code. Originally committed as part
of svn 808523.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@808945 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/util/StringUtil.java",
"hunks": [
{
"added": [],
"header": "@@ -24,9 +24,6 @@ package org.apache.derby.iapi.util;",
"removed": [
"import java.util.regex.Pattern;",
"import java.util.regex.Matcher;",
""
... |
derby-DERBY-4087-996c8945 | DERBY-4087 Clean up debug printing of the abstract syntax trees after parsing, binding and optimization
Temporary roll-back of changes (808523) to the statistics printing,
because they broke some old harness tests to change. It will take a
while to establish correctness of new masters, so rolling back for
now. Expect to roll forward again soon, though.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@808601 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/rts/RealDistinctScanStatistics.java",
"hunks": [
{
"added": [],
"header": "@@ -28,7 +28,6 @@ import org.apache.derby.catalog.UUID;",
"removed": [
"import org.apache.derby.iapi.util.StringUtil;"
]
}... |
derby-DERBY-4087-ae848fda | DERBY-4087 Clean up debug printing of the abstract syntax trees after parsing, binding and optimization
Follow-up patch, derby-4087-statistics. This fixes the wrong indentation seen
in runtimestatistics for scan qualifiers.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@809632 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/rts/RealDistinctScanStatistics.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.StringUtil;"
],
"header": "@@ -28,6 +28,7 @@ import org.apache.derby.catalog.UUID;",
"removed": []
}... |
derby-DERBY-4087-c9a12062 | DERBY-4087 Clean up debug printing of the abstract syntax trees after parsing, binding and optimization
Patch DERBY-4087-b, which improves debug-time printing of query trees.
Much of the changes concerns cleaning up when to use toString and when
to use printSubNodes, a pattern which is well-defined but was severely
broken, as well as including more data for each node, and sub-trees
not hitherto printed at all. Please see JIRA for mroe detail.
A new feature highlights aliases by suppressing printing of already
printed subtrees (the query tree is a DAG, not a pure tree).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@808523 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/conn/LanguageConnectionContext.java",
"hunks": [
{
"added": [
"import java.util.AbstractMap;"
],
"header": "@@ -48,6 +48,7 @@ import org.apache.derby.iapi.sql.execute.RunTimeStatistics;",
"removed": []
}
... |
derby-DERBY-4088-7062abe7 | DERBY-4088: DDMReader readBytes ArrayIndexOutOfBoundsException
When ensureBLayerDataInBuffer() calls compressBLayerData() the number
of bytes in the buffer is reduced (header bytes are stripped out) and
there might be too little data in the buffer when it returns. This
patch fixes the problem by ensuring that compressBLayerData() fills
the buffer with enough extra bytes to compensate for the removal of
the header bytes.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@752813 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DDMReader.java",
"hunks": [
{
"added": [
" // Offset from the start of the valid region of the byte buffer,",
" // pointing to the start of the DSS we're looking at.",
" int tempOffset = 0;",
... |
derby-DERBY-4088-f582a777 | DERBY-4088: DDMReader readBytes ArrayIndexOutOfBoundsException
Reverted the previous fix (revision 752813) in compressBLayerData()
and instead changed ensureBLayerDataInBuffer() to match the
corresponding method in Reply.java on the client side.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@755866 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DDMReader.java",
"hunks": [
{
"added": [
" if (dssIsContinued && (desiredDataSize > dssLength)) {",
" // The data that we want is split across multiple DSSs",
" int continueDssHeaderCount... |
derby-DERBY-4092-425fcc91 | DERBY-4092: Don't allow invocations of table functions in contexts which expect a scalar function return value.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@805443 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/JavaToSQLValueNode.java",
"hunks": [
{
"added": [
"import org.apache.derby.catalog.TypeDescriptor;"
],
"header": "@@ -21,6 +21,7 @@",
"removed": []
}
]
}
] |
derby-DERBY-4095-c7e05da0 | DERBY-4095 Trigger in fails with ERROR 38000: The exception 'java.sql.SQLException: ResultSet not open during VTIResultSet.getNextRowCore()
Reinitialize the ResultSet on executeQuery of TriggerNewTransitionRows and TriggerOldTransitionRows so that for a nested loop join, reopening the ResultSet does not result in an exception.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@756516 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/TriggerNewTransitionRows.java",
"hunks": [
{
"added": [
"\t\tinitializeResultSet();",
"\t}",
"",
"\tprivate ResultSet initializeResultSet() throws SQLException {",
"\t\tif (resultSet != null)",
... |
derby-DERBY-4097-465c7c7d | DERBY-4097: BatchUpdateException in NullableUniqueConstraintTest
Improve error reporting when a BatchUpdateException is thrown by the
client driver. Use initCause() to put the underlying exception in the
chain of exceptions printed by printStackTrace(). Note that there may
be more than one underlying exception for a BatchUpdateException and
only one of them will be printed by printStackTrace(). To see the rest
of the exceptions, getNextException() has to be used (as before).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@755147 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/BatchUpdateException.java",
"hunks": [
{
"added": [
" Object[] args, int[] updateCounts, SqlException cause)"
],
"header": "@@ -37,7 +37,7 @@ public class BatchUpdateException extends java.sql.BatchUpdateExcepti... |
derby-DERBY-4102-e0939287 | DERBY-4102: Assert failure or ClassCastException in EmbedBlob when retrieving BLOB >= 32K.
Made Derby store the stream content to a temporary location when it knows the stream isn't resetable. Small streams (< 32K) will be stored in memory, larger streams will be written to disk (the switch happens transparently).
Added the repro as a regression test.
Patch file: derby-4102-1a.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@835286 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/EmbedBlob.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.types.RawToBinaryFormatStream;"
],
"header": "@@ -27,6 +27,7 @@ import org.apache.derby.iapi.error.StandardException;",
"removed": []
... |
derby-DERBY-4110-190e5231 | DERBY-4110: Deleting from a table with its synonym throws an exception
When building the ResultColumnList that is used to tie together the
search results from the WHERE clause with the processing of the DELETE,
the result columns will be bound against the exposed table name of the
table named in the DELETE statement, so if the statement used a
synonymTableName, then the result column list should manufacture column
references which use a synonymTableName as well.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@896722 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4115-a6a07338 | DERBY-4115 Provide a way to drop statistics information
The details of all the changes in this commit are listed below.
1)Added a new routine SYSCS_DROP_STATISTICS, with public access similar to SYSCS_UPDATE_STATISTICS. This happens in DataDictionaryImpl, where SYSCS_DROP_STATISTICS is added to the list of public access procedures in sysUtilProceduresWithPublicAccess
2)The new stored procedure implementation is similar to update statistics, ie allow the routine to go through ALTER TABLE where permission/privilege checking, table/schema/index name validations happen automatically and we implement the routine logic through extension of ALTER TABLE syntax. This new syntax for ALTER TABLE syntax(same as we did for update statistics) is an internal syntax only and won't be available to an end user directly.
3)This commit changes sqlgrammar.jj to recognize the following internal syntaxes for ALTER TABLE
a)ALTER TABLE tablename ALL DROP STATISTICS
The existing(corresponding syntax) for update statistics is as follows
ALTER TABLE tablename ALL UPDATE STATISTICS
b)ALTER TABLE tablename STATISTICS DROP indexname
The existing(corresponding syntax) for update statistics is as follows
ALTER TABLE tablename UPDATE STATISTICS indexname
Notice the two syntaxes for index level statistics are different for drop vs update.(the reason for the syntax difference is explained above)
4)After the statistics are dropped, we send invalidation signal to dependent statements so they would get recompiled when they are executed next time. This will make sure that they pick the correct plan given the statistics for the table.
5)The commit takes care of some of the test failures(expected failures because of the addition of a new system procedure).
6)The commit adds basic upgrade test for the new procedure. This test ensures that drop statistics procedure is available only after hard upgrade.
7)While writing the upgrade tests, I found that a meaningful test for drop statistics could only be written for Derby releases 10.5 and higher. We have found that when constraints end up sharing same backing index, Derby won't create statistics for them. This is issue DERBY-5702. But if we run update statistics on that constraint, we will be able to get the statistics for such a constraint. Later, when the constraint is dropped, because of DERBY-5681, the statistics row for such a constraint(one that shares it's backing index with another constraint) is never dropped. We can use drop statistics procedure introduced in this jira to take care of such hanging indexes. But since update statistics procedure is only available in 10.5 and higher, I couldn't demonstrate use of drop statistics to drop hanging statistics rows.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1338017 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/SystemProcedures.java",
"hunks": [
{
"added": [
"\t * @exception SQLException"
],
"header": "@@ -733,7 +733,7 @@ public class SystemProcedures {",
"removed": [
"\t * @exception StandardException Sta... |
derby-DERBY-4115-c1e0f8ee | DERBY-4115/DERBY-5681: Provide a way to drop statistics information
Moved upgrade test from BasicSetup to Changes10_9.
Includes some simplifications that could be made because of the move.
Patch file: derby-4115-7a-move_test.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1341059 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4116-02f8e49b | DERBY-4116 SYSCS_UTIL.SYSCS_UPDATE_STATISTICS should update the store estimated row count for the table
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@760497 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/AlterTableConstantAction.java",
"hunks": [
{
"added": [
"\t\t//initialize numRows to -1 so we can tell if we scanned an index.\t",
"\t\tlong numRows = -1;\t\t",
"\t\t"
],
"header": "@@ -645,7... |
derby-DERBY-4119-cf2105b3 | DERBY-4119: Compress on a large table fails with IllegalArgumentException - Illegal Capacity
Use long arithmetic to prevent overflow in intermediate results when
increasing the capacity of NodeAllocator. Also make sure that the Node
array does not exceed maxSize, and allow the sort to continue even if
a larger array cannot be allocated.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@760422 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/sort/NodeAllocator.java",
"hunks": [
{
"added": [
" // Calculate the new length. The new array should be no longer",
" // than maxSize. Use a long for the intermediate result to prevent",
... |
derby-DERBY-412-e214c072 | DERBY-412 - Connection toString should show type information and the meaning of the identifier that it prints - Patch by David Van Couvering(David.Vancouvering@Sun.COM)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@230523 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection.java",
"hunks": [
{
"added": [
" private String connString;"
],
"header": "@@ -51,6 +51,7 @@ public class BrokeredConnection implements Connection",
"removed": []
}
]
},
... |
derby-DERBY-4122-5b9a6d9b | DERBY-4122: java/testing/org/apache/derbyTesting/unitTests/junit/ReaderToUTF8StreamTest.java.
Added mark/reset functionality to ReaderToUTF8Stream.
Made SQLClob use mark/reset to rewind the data stream when too many bytes are
read as part of the stream header parsing. This happens when reading Clobs
written with the pre-10.5 header format, either in soft or hard upgraded
databases.
Added a new error message.
Added unit tests for mark/reset.
Patch file: derby-4122-4c-classcast_fix_mark_reset.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@762384 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/ReaderToUTF8Stream.java",
"hunks": [
{
"added": [
"import org.apache.derby.shared.common.reference.MessageId;"
],
"header": "@@ -30,6 +30,7 @@ import org.apache.derby.iapi.services.i18n.MessageService;",
"remo... |
derby-DERBY-4124-2ca6c802 | DERBY-4124: Remove double-checked-locking from EmbeddedDataSource.findDriver
This change ensures that EmbeddedDataSource.findDriver always synchronizes
its access to the 'driver' member variable. The previous code performed
unsynchronized access to the field, and then, depending on the results of
the unsynchronized access, performed synchronized access.
This double-checked-locking idiom is unsafe and incorrect, and this change
replaces it with a simpler always-synchronized access.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@833888 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/jdbc/EmbeddedDataSource.java",
"hunks": [
{
"added": [
"\t\tsynchronized(this)",
"\t\t\t// The driver has either never been booted, or it has been",
"\t\t\t// shutdown by a 'jdbc:derby:;shutdown=true'",
"\t\t\tif (... |
derby-DERBY-4125-20e986d5 | DERBY-4125: The in-memory storage back end doesn't work on Windows.
Changed the in-memory storage factory to rely much more on java.io.File to
handle paths and names.
The data store now stores all files and directories with normalized paths.
Also fixed a bug in DataStore.deleteEntry for deletion of directories.
Added two more tests; testListChildren and testCreateRoot.
Patch file: derby-4125-1a-improved_path_handling.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@759176 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/io/VFMemoryStorageFactory.java",
"hunks": [
{
"added": [
" store.purge();"
],
"header": "@@ -58,7 +58,7 @@ public class VFMemoryStorageFactory",
"removed": [
" store.deleteAll... |
derby-DERBY-4126-4d0fc78c | DERBY-4126: Find table functions even when they are in jar files in the database.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@759360 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromVTI.java",
"hunks": [
{
"added": [
" Class vtiClass = lookupClass( className );",
" Class vtiCostingClass = lookupClass( VTICosting.class.getName() );",
" try {",... |
derby-DERBY-4127-1cd97e82 | DERBY-4127: Port 764471 from 10.5 branch to main.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@764481 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DD_Version.java",
"hunks": [
{
"added": [
"import java.util.HashSet;"
],
"header": "@@ -61,6 +61,7 @@ import java.io.ObjectInput;",
"removed": []
},
{
"added": [
" Ha... |
derby-DERBY-4137-849dab23 | DERBY-4137: OOM issue using XA with timeouts
Reduce the memory footprint when executing successful XA transactions that
have a timeout set by nulling out the reference to the XATransactionState
object in the timer task. The timer task will stay around in the timer queue
until reaching the scheduled time - even if the task is canceled.
Added a regression test (run as part of 'ant junit-lowmem').
Patch file: derby-4137-2a-reduce_memory_footprint.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1136363 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/jdbc/XATransactionState.java",
"hunks": [
{
"added": [
" private static class CancelXATransactionTask extends TimerTask {",
" private XATransactionState xaState; ",
"",
" /**",
" ... |
derby-DERBY-4141-31ba8d0a | DERBY-4141 XAExceptions thrown by Derby can have errorCode 0
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@764495 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetXAResource.java",
"hunks": [
{
"added": [
" rc = getSqlExceptionXAErrorCode(sqle);"
],
"header": "@@ -167,7 +167,7 @@ public class NetXAResource implements XAResource {",
"removed": [
"... |
derby-DERBY-4145-7168d7da | DERBY-4145: Look for illegal references in generation clauses before binding the clauses.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@762520 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/TableElementList.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.sql.dictionary.ColumnDescriptorList;"
],
"header": "@@ -36,6 +36,7 @@ import org.apache.derby.iapi.types.TypeId;",
"removed":... |
derby-DERBY-4146-a8c09662 | DERBY-4146: Bind a column descriptor to a generated result column for INSERTs without target lists.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@763230 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4149-58355bbd | DERBY-4149 test failure in jdbcapi.InternationalConnectSimpleDSTest fixture testSimpleDSConnect on IBM iseries - Database '?' not found.
Fix the test so that it cleans up the database directory even if connection fails. This does not correct the actual test failure, just the cleanup.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@822027 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4149-6c42ee6d | DERBY-4149; test failure in jdbcapi.InternationalConnectSimpleDSTest
- skipping the fixtures in InternationalConnectSimpleDSTest and
InternationalConnectTest on iseries.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1058707 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4149-cd5b86ca | DERBY-4149; test failure in jdbcapi.InternationalConnectSimpleDSTest fixture testSimpleDSConnect on IBM iseries - Database '?' not found.
reinstating the skipped test cases after fix of jvm on iseries
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1245283 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-415-32803bce | DERBY-415 : sysinfo with -cp client should not complain about DB2 Driver
This change modifies the behavior of the "-cp client" argument to the
sysinfo tool. Formerly, this argument checked for both the DerbyNetClient
and the DB2 JCC driver, and complained if both drivers were not present.
Increasingly, users of Derby are using just the DerbyNetClient, and the use
of the JCC driver is less common, so it makes sense that "-cp client" should
focus on the DerbyNetClient, and the DB2 JCC driver can be treated separately.
So, "-cp client" now only checks for the DerbyNetClient, and a new argument
"-cp db2driver" is added to check for the DB2 JCC driver. The new behavior is:
java sysinfo -cp: checks all the various components of the classpath
java sysinfo -cp client: just checks the network client
java sysinfo -cp db2driver: just checks the JCC driver
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@431741 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/sysinfo/Main.java",
"hunks": [
{
"added": [
"\tprivate static final String DB2DRIVER = \"db2driver\";",
"\tprivate static final String USAGESTRINGPARTA = MAINUSAGESTRING + \" [ [ \" + EMBEDDED + \" ][ \" + NET + \" ][ \" + C... |
derby-DERBY-4154-7feaf9c0 | DERBY-4154 DboPowersTest should not hard upgrade the system/wombat database
The patch makes the hard upgrade fixture use another database than
"system/wombat", by wrapping the offending test cases in a
singleUseDatabaseDecorator.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@788369 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4157-6409b407 | DERBY-4157: Add a test for the integrity of metadata along all upgrade trajectories--the test must be run standalone and is not wired into our regression test suite.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@785826 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4157-e65365e6 | DERBY-4157 (partial) Create a test to verify that virgin metadata is identical to hard-upgraded metadata
Contributed by Rick Hillegas
Attaching derby-4157-01-aa-refactor.diff. This patch is a first step toward writing the new test. This patch factors out some of the existing upgrade test machinery so that the new test can re-use that machinery:
1) logic to discover old versions
2) logic to create class loaders out of those old versions
3) logic to use those class loaders
Touches the following files:
A java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
A java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/UpgradeClassLoader.java
New classes to hold the logic which has been factored out. OldVersions used to be an inner class of _Suite. UpgradeClassLoader consists of code extracted from UpgradeRun and PhaseChanger.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@764912 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4160-fed9c08f | DERBY-4160: getMetaData().getIndexInfo crashes with "ERROR X0Y68: Column 'PARAM1' already exists."
Use a shared code path for adding parameters to SYS.SYSCOLUMNS on the
first compilation and subsequent compilations of a meta-data query.
Previously, the first compilation took a different code path, but that
caused problems if two threads compiled a meta-data query at the same
time, and both threads thought they were first.
Set a savepoint before attempting to write a stored prepared statement
to the system tables in a nested transaction, and roll back to the
savepoint if an error happens. This prevents partially stored prepared
statements from lying around in the system tables after an error.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1570488 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/dictionary/SPSDescriptor.java",
"hunks": [
{
"added": [
" private final boolean initiallyCompilable;"
],
"header": "@@ -137,7 +137,7 @@ public class SPSDescriptor extends UniqueSQLObjectDescriptor",
"remove... |
derby-DERBY-4166-a216dfd4 | DERBY-4166 improvements to the mailjdbc test
Contributed by Lily Wei lilywei@yahoo.com
- Changed schema to allow multiple attachments.
- Increase sleep time between threads to avoid deadlocks.
- Restructure refresh thread to more accurately reflect mail retrieval.
- maintain 10 - 56 rows during test to keep size predictable.
- Make sure all transactions are commited or rolled back to avoid locking issues.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@921070 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/system/mailjdbc/tasks/Browse.java",
"hunks": [
{
"added": [
"\t\t\t\t//Try to avoid deadlock situation with delete from Refresh thread",
"\t\t\t\tThread.sleep(100000);",
"\t\t\t\t//Checking whether Refresh thread is ... |
derby-DERBY-4166-d9e100c4 | DERBY-4166 (partial) improvements to the mailjdbc test
Make databaseSize a recursive method to calculate the disk usage properly
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@795310 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/system/mailjdbc/utils/DbTasks.java",
"hunks": [
{
"added": [
"\t\tlong dbsize = databaseSize(new File(\"mailsdb\"));"
],
"header": "@@ -621,7 +621,7 @@ public class DbTasks {",
"removed": [
"\t\tlong db... |
derby-DERBY-417-fcfc9254 | DERBY-417: Remove hardcoded references to encryption providers in Beetle6038 and
let Derby choose the correct encryption provider. This allows the test to pass
on Mac OS X and any other JVM where the vendor is not Sun or IBM.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@380287 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4171-5bef31e2 | DERBY-4171: Connections to on-disk db go to in-memory db if in-memory db with same name is booted.
If the storage factory isn't the default one (DIRECTORY), don't allow
connections without a subsubprotocol specified.
Added a test.
Patch file: derby-4171-1b-fix.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@782954 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4175-84fa650c | DERBY-4175 Instability in some replication tests under load, since tests don't wait long enough for final state or anticipate intermediate states
Patch derby-4175-3 (+ resolved some conflicts arising from commit of DERBY-3417).
It makes three replication tests less sensitive to load by making
them accept intermediate states without failing or wait for longer
before giving up on seeing the final end state of a replication state
change.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@769602 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4177-8654374d | DERBY-4177: Javadoc for BTreeLockingPolicy should not mention "scan lock"
The fix for DERBY-2991 removed the concept of a "scan lock" and
RECORD_ID_PROTECTION_HANDLE, so the javadoc for the BTreeLockingPolicy
class hierarchy should not mention them anymore.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@775937 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreeLockingPolicy.java",
"hunks": [
{
"added": [],
"header": "@@ -24,7 +24,6 @@ package org.apache.derby.impl.store.access.btree;",
"removed": [
"import org.apache.derby.iapi.store.raw.RecordHandle;"
... |
derby-DERBY-4179-0c7cea74 | DERBY-4179 bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
Followup comment fix.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@942480 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4179-6c65c08d | DERBY-4179 bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
Follow-up simplification patch, which replaces the home-grown system
property setup/teardown code with the standard
SystemPropertyTestSetup.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@942587 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4179-6e930481 | DERBY-4179 bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
Followup patch, doc and comment changes only.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@942476 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4179-8badf993 | DERBY-4179 bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
Patch derby-4179-junit-5:
* Rewrite of boot lock test to JUnit, this also solves the problem
with running with jars in relative classpaths.
* Added test of effectiveness of derby.database.forceDatabaseLock for
phoneME platforms, until we implement DERBY-4646. (I could not find
any other such test).
* Fixed JUnit harness to correctly fork a Sun phoneME vm (image name
is cvm, not java),
* Added logic to capture what happens to minion (if it fails) by
capturing its stderr (if it ever gets started, that is), cf. example enclosed.
* Added socket logic to communicate to parent when minion has booted
the "dual boot" candidate to avoid having to wait for 30 seconds or
more to be sure it has done so. Test now runs in a few seconds.
* Skips test for j9 for now, since this platform fails on the fork
operation according to Kathey, cf DERBY-4647.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@942286 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/TestConfiguration.java",
"hunks": [
{
"added": [
"",
" /**",
" * Decorate a test to use a new database that is created upon the first",
" * connection request to the database and shutdown &... |
derby-DERBY-418-68c8e7d8 | DERBY-418: outofmemory error when running large query in autocommit=false mode
DERBY-1142: Metadata calls leak memory
Notify GenericLanguageConnectionContext when activations are marked as
unused, and clean up unused activations when a new one is added.
Patch contributed by Mayuresh Nirhali.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@439279 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java",
"hunks": [
{
"added": [
"\tprivate volatile boolean unusedActs=false;"
],
"header": "@@ -116,6 +116,7 @@ public class GenericLanguageConnectionContext",
"removed": []... |
derby-DERBY-4182-8b553f1c | DERBY-4182
Before this fix abort of inserts that included clob or blob chains would
destroy the links of the allocated pages of the chains. This would leave
allocated pages that could never be reclaimed either by subsequent post
commit processing or inplace compress. Only offline compress could reclaim
the space. This fix changes insert abort processing to automatically put
all pieces of long columns except for the head page on the free list as part
of the abort.
Note this does not fix existing tables that have had this problem happen in
the past, only stops it from happening. One must run an offline compress to
reclaim this space to fix any instances of this bug prior to this fix.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@778926 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/BasePage.java",
"hunks": [
{
"added": [
" /**",
" * Routine to insert a long column.",
" * <p>",
" * This code inserts a long column as a linked list of rows on overflow",
... |
derby-DERBY-4186-72b50c0c | DERBY-4186 After master stop, test fails when it succeeds in connecting (rebooting) shut-down ex-slave
Patch derby-4186-2, which solves this issue by
a) fixing a bug in SlaveDataBase, which loses and exception iff a
command to stop replication arrives from the master to the slave
before the initial connection (successful slave started) command
returns. This is a corner case race condition, and not very likely to
occur in practice, since it makes little sense to stop replication
immediately after starting it.
b) fixing a bug in the test, which switched on its head what is really
expected behavior, and also adds a waiting loop to allow intermediate
state on slave after the master is stopped. Also fixed some erroneous
comment and removed some cruft.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@769962 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/db/SlaveDatabase.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.error.ExceptionSeverity;"
],
"header": "@@ -25,6 +25,7 @@ import org.apache.derby.iapi.error.PublicAPI;",
"removed": []
},
{
... |
derby-DERBY-4191-46df2550 | DERBY-4191
Require minimum select privilege from the tables in the SELECT sql if no column is selected from the table by the user eg
select count(*) from root.t;
select 1 from root.t;
For the query above, Derby was letting the user execute the select even if the user had no select privilege available on root.t With this fix, Derby will check if there is atleast one column on which the user has select privilege available to it or if the user select privilege at the table level. If yes, only then the user will be able to select from another user's table.
select myTable.a from myTable, admin.privateTable
for the query above, since no column is selected specifically from admin.privateTable, Derby will now see if there is table level select privilege or atleast one column level select privilege available on admin.privatTable
One other problem scenario was
update ruth.t_ruth set a = ( select max(c) from ruth.v_ruth );
For the query above, prior to fix for DERBY-4191, we were not looking for select privilege for the subquery. That has also been fixed with fix for DERBY-4191
All the existing tests passed with no regression. Added few tests for the fixes involved in this jira.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@898635 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/dictionary/StatementColumnPermission.java",
"hunks": [
{
"added": [
"\t\t",
"\t\t//DERBY-4191",
"\t\t//If we are looking for select privilege on ANY column,",
"\t\t//then we can quit as soon as we find som... |
derby-DERBY-4193-be4b84e8 | DERBY-4193: ASSERT FAILED Scan position already saved with multi-threaded insert/update/delete
Forget about the current position before trying to reposition on the
end point of a scan. Then the ASSERT won't be confused if it needs to
save the position again (it fails if it finds that a position is
already saved).
BTreeScan.positionAtStartForBackwardScan() also had this problem, but
since it doesn't have any callers, this method was removed instead of
being fixed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@772090 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/btree/BTreeScan.java",
"hunks": [
{
"added": [
" // Forget the current position since we'll use the start key",
" // to reposition on the start of the scan.",
" ... |
derby-DERBY-4198-7d0f620f | DERBY-4198 When using the FOR UPDATE OF clause with SUR (Scroll-insensive updatable result sets), the updateRow() method crashes
Patch derby-4198-4. This is the second part of the solution for this
issue. It solves the issue of column mapping in the presence of named
columns in a FOR UPDATE OF clause. The original code was not general
enough; ScrollInsensitiveResultSet.updateRow needs to make use of
RowChanger to do the right thing.
The patch also adds new test cases.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@785163 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/execute/NoPutResultSet.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.sql.execute.RowChanger;"
],
"header": "@@ -24,6 +24,7 @@ package org.apache.derby.iapi.sql.execute;",
"removed": []
}
... |
derby-DERBY-4199-fe7db0f9 | DERBY-4199: Write exceptions to file in the fail directory as they occur with JUnit tests.
Write exceptions being thrown during JUnit testing to file as soon as they
happen. The output file is called 'error-stacktrace.out' and is located under
the fail-directory. If the output file already exists, the new output is
appended.
Added a new method for opening a file in append mode (in a privileged block).
Patch file: derby-4199-1a-writeExceptionsToFile.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@774729 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4201-210e0349 | DERBY-4201: SecureServerTest AssertionFailedError: Timed out waiting for network server to start
Wait until server instances from earlier test cases have released the
server port before starting a new server.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1210846 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/NetworkServerTestSetup.java",
"hunks": [
{
"added": [
"import java.net.ServerSocket;"
],
"header": "@@ -24,8 +24,8 @@ import java.net.InetAddress;",
"removed": [
"import java.io.InputStream;"
... |
derby-DERBY-4203-934f02da | DERBY-4203 (partial) Change mailjdbc system test to be able to restart with the existing database instead of creating a new one so it can be used for upgrade testing
This patch does not include the sttest changes.
Contrubuted by Lily Wei (lilywei at yahoo dot com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@795166 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/system/mailjdbc/utils/DbTasks.java",
"hunks": [
{
"added": [
"\t/**",
"\t * jdbcLoad - Create url, schema and set driver and database system property that will be use later in the test.",
"\t * @param driverType - \"... |
derby-DERBY-4204-698ab621 | DERBY-4204: Runtime statistics not collected on re-execution of statement
Make sure NoRowsResultSetImpl.close() prints the collected runtime
statistics each time close() is called on a result set that is not
currently closed. After DERBY-827 close() didn't print the statistics
if the result set had been closed and reopened.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@774281 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/NoRowsResultSetImpl.java",
"hunks": [
{
"added": [],
"header": "@@ -62,7 +62,6 @@ import org.apache.derby.iapi.types.DataValueDescriptor;",
"removed": [
"\tprivate boolean dumpedStats;"
]
},
... |
derby-DERBY-4204-6b03ead6 | DERBY-4204: Statistics not collected on re-execution of statement
This change enhances the DERBY-4204 regression test to verify that the
XPLAIN table form of statistics collection is also re-collected on each
statement re-execution. Without the DERBY-4204 fix, re-execution of DML
statements was only resulting in a single row in the SYSXPLAIN_STATEMENTS
table, while after the fix, the correct results of 5 rows are observed.
This change should NOT be backported to 10.5 and earlier branches, because
it depends on the XPLAIN functionality.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@774830 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4208-00c7a208 | DERBY-4208 Parameters ? with OFFSET and/or FETCH
This patch implements the use of dynamic parameters with OFFSET/FETCH and adds new tests.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@807337 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/execute/ResultSetFactory.java",
"hunks": [
{
"added": [
"\t * @param offsetMethod The OFFSET parameter was specified",
"\t * @param fetchFirstMethod The FETCH FIRST/NEXT parameter was",
"\t * ... |
derby-DERBY-4212-06154a0a | DERBY-4212: Prepared statement with OFFSET/FETCH gives different results on subsequent execute
Added a test case to OffsetFetchNextTest (disabled for now).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@771613 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4212-640d05d6 | DERBY-4212 Prepared statement with OFFSET/FETCH gives different results on subsequent execute
Patch DERBY-4212-2, which fixes this issue by resetting state
variables in the close method of RowCountResultSet, and adds a new
test case for this use case to OffsetFetchNextTest.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@772299 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/RowCountResultSet.java",
"hunks": [
{
"added": [
" final private long offset;",
" final private long fetchFirst;",
"",
" /**",
" * True if we haven't yet fetched any rows fro... |
derby-DERBY-4213-bbde6187 | DERBY-4213; sttest needs to be adjusted to not run out of disk space
this change modifies the test in 2 ways:
- add in-place-compress so occasionally unused space gets released
- adjust the code that picks rows for delete so more rows will get deleted
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@806699 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/system/sttest/utils/CompressTable.java",
"hunks": [
{
"added": [
"import java.sql.CallableStatement;"
],
"header": "@@ -21,10 +21,10 @@",
"removed": [
"import java.sql.Statement;"
]
}
... |
derby-DERBY-4214-a61fd536 | DERBY-4214: Fix signature of CLOBGETSUBSTRING during hard-upgrade to 10.6.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@787310 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4215-b05fa6ea | DERBY-4215: remove bad permissions tuple during 10.6 upgrade.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@787754 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DD_Version.java",
"hunks": [
{
"added": [
" //",
" // Change the return type of SYSIBM.CLOBGETSUBSTRING if necessary. See",
" //"
],
"header": "@@ -451,11 +451,13 @@ publ... |
derby-DERBY-4218-c5d9be33 | DERBY-4218: "Table/View 'MAX_SCAN' does not exist" in IndexSplitDeadlockTest
Wait for all threads to finish before dropping tables in tearDown().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@772534 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4223-a39c84c1 | DERBY-4223 Provide the ability to use properties with ij.runScript()
adds a new runScript method that allows use of system properties with runScript.
DERBY-4217 (partial) adds use derby.tests.port system property when initializing TestConfiguration.
Contributed by Tiago Espinha (tiago at espinhas dot net)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@781200 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/TestConfiguration.java",
"hunks": [
{
"added": [
"",
" /**",
" * Return a decorator for the passed in tests that sets the",
" * configuration for the client to be Derby's JDBC client",
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.