id stringlengths 22 25 | commit_message stringlengths 137 6.96k | diffs listlengths 0 63 |
|---|---|---|
derby-DERBY-4677-012a72b2 | DERBY-4677
We were not transferring unique nullable properties from the system catalog to the store layer during compress table and bulk insert. Because of that, after those operations, we started allowing duplicate rows those causing db corruption. With this checkin, we will be transferring unique nullable properties from sql layer to store layer. System catalogs have the information correct, but unique nullability information was not getting transferred to store during btree recreation in case of compress table and bulk insert operations.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@954544 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/InsertResultSet.java",
"hunks": [
{
"added": [
"\t\t\tif(cd.getIndexDescriptor().isUniqueWithDuplicateNulls())",
"\t\t\t{",
"\t\t\t\tproperties.put(",
"\t \"uniqueWithDuplicateNu... |
derby-DERBY-4679-125f9182 | DERBY-4679 Several left outer joins causes unstable query with incorrect results
Patch derby-4679b, which solves the following problem:
When transitive closure generates new criteria into the query, it is
sometimes confused by situations where the same column name appears in
a result column list multiple times due to flattening of sub-queries.
Flattening requires remapping of (table, column) numbers in column
references. In cases where the same column name appears in a result
column list multiple times, this lead to remapping (reassigning) wrong
(table, column) numbers to column references in join predicates
transformed to where clauses as a result of the flattening.
See also DERBY-2526 and DERBY-3023 whose fixes which were partial
solutions to the problem of wrong column number remappings confusing
the transitive closure of search predicates performed by the
preprocessing step of the optimizer.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@952237 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ColumnReference.java",
"hunks": [
{
"added": [
" /* For remembering original (tn,cn) of this CR during join flattening. */",
" private int tableNumberBeforeFlattening = -1;",
" private int columnNum... |
derby-DERBY-4679-4ce669e5 | DERBY-4679 Several left outer joins causes unstable query with incorrect results
Follow-up patch derby-4679-followup, which makes the original patch
safer by also matching the column name once a candidate result column
has been located using the table number and column number pair to
match an RC. This is to safe-guard against false matches, since
DERBY-4595 shows that the column number can be wrong in certain
situations.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@957260 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ResultColumnList.java",
"hunks": [
{
"added": [
" * <p/>",
" * {@code columnName} is used to assert that we find the right column.",
" * If we found a match on (tn, cn) but columnName is wrong, r... |
derby-DERBY-4679-b26c1ca2 | DERBY-4679 Several left outer joins causes unstable query with incorrect results
Follow-up patch derby-4679-2a, which makes the new (tn, cn) based
remapping work also for a CR to a subquery join participant being rebound
after flattening, see detailed comments in the code. Extra test cases
are added to JoinTest#testDerby_4679
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@958618 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ResultColumnList.java",
"hunks": [
{
"added": [
" * cf. DERBY-4695, we could remove this parameter."
],
"header": "@@ -325,7 +325,7 @@ public class ResultColumnList extends QueryTreeNodeVector",
"rem... |
derby-DERBY-4684-1b3f93b3 | DERBY-4684: Fix implicit casts to BOOLEAN.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@951047 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/SQLBoolean.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.reference.SQLState;"
],
"header": "@@ -30,6 +30,7 @@ import org.apache.derby.iapi.services.io.Storable;",
"removed": []
}
]
}... |
derby-DERBY-4685-20cc6f64 | DERBY-4685: Dead/unreachable code in OpenConglomerate.lockPositionForWrite()
Remove the second parameter (forInsert) in lockPositionForWrite()
because it is always false in the current code, and because the method
is not believed to work for inserts.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1028712 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/access/conglomerate/GenericConglomerateController.java",
"hunks": [
{
"added": [
" open_conglom.lockPositionForWrite(pos, true);"
],
"header": "@@ -176,7 +176,7 @@ public abstract class GenericConglomerateContr... |
derby-DERBY-4686-33288d68 | DERBY-4686: SQLBinary.writeBlob is inefficient, reading one byte at a time from the source BLOB
Improves performance by reading and writing from/to a transfer buffer.
Patch contributed by Yun Lee (yun dot lee dot bj at gmail dot com).
Patch file: DERBY-4686-1.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@954748 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/SQLBinary.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.services.io.DerbyIOException;"
],
"header": "@@ -31,6 +31,7 @@ import org.apache.derby.iapi.types.DataValueDescriptor;",
"removed": []
... |
derby-DERBY-4692-6ad8107b | DERBY-4692: Forbid UNIONs between BOOLEAN and non-BOOLEAN types, per the SQL Standard.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@952263 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ResultColumnList.java",
"hunks": [
{
"added": [
"\t\t\t** Check type compatability.",
"\t\t\tif ( !unionCompatible( thisExpr, otherExpr ) )"
],
"header": "@@ -2373,14 +2373,10 @@ public class ResultCol... |
derby-DERBY-4693-3c3fb736 | DERBY-4693: RENAME COLUMN loses IDENTITY attributes
This change modifies the RENAME COLUMN logic so that it preserves the
autoincrement properties of the column when renaming it. Since RENAME
COLUMN more-or-less drops and re-adds the column, we need to ensure
that when the column is re-added, if it is an Autoincrement column,
we set the CREATE_AUTOINCREMENT flag that the parser sets when
initially creating the table.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@954344 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/RenameConstantAction.java",
"hunks": [
{
"added": [
"import org.apache.derby.impl.sql.compile.ColumnDefinitionNode;"
],
"header": "@@ -50,6 +50,7 @@ import org.apache.derby.catalog.UUID;",
"removed": []
... |
derby-DERBY-4694-65213c4f | DERBY-4694: Build breaks on Mac OS X due to JDK classpath issues
Relaxed verification criteria for Apple JDKs (skip check for Headers directory).
Added flag -DprintCompilerPropertiesVerbose to aid debugging when the
property setter fails to set the correct compile classpath(s).
Patch file: derby-4694-2b-debugging_and_mac_fix.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@963206 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyPreBuild/PropertySetter.java",
"hunks": [
{
"added": [],
"header": "@@ -123,10 +123,8 @@ public class PropertySetter extends Task",
"removed": [
" private static final String APPLE_JAVA_ROOT = \"/System/Library/Frameworks/J... |
derby-DERBY-4694-ee6ea33e | DERBY-4694: Build breaks on OS X due to JDK classpath issues.
Enabled JAR inspection for Mac OS X instead of using hard-coded values.
The motivation for the change is that Apple has started symlinking the
directories for JDK 1.4 and JDK 1.5 to JDK 1.6. This made the build fail on
OS X (only recent fresh installs, where the symlinking is used).
Patch file: derby-4694-1b.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@958555 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyPreBuild/PropertySetter.java",
"hunks": [
{
"added": [],
"header": "@@ -23,7 +23,6 @@ package org.apache.derbyPreBuild;",
"removed": [
"import java.io.FilenameFilter;"
]
},
{
"added": [
" p... |
derby-DERBY-4695-ee21e7c1 | DERBY-4695 Internal assignment of tablenumer, columnnumber looks wrong in query tree, although no ill effects are seen
Patch derby-4695-fixcolumnno-1b, which moves the assignment of
ColumnReference#columnnumber from ColumnReference to the underlying
FromTable, i.e. the same place as where the table number is
assigned. This assures that the two are in synch, and the columnNumber
assignment is no longer thwarted by the (re)assignment of the
ColumnReference#source for "JoinNode"s to one of the result columns of
the Join itself (needed for code generation: the source for the
ColumnReference need to be to the correct ResultSet at generate time,
cf the comment in JoinNode#getMatchingColumn).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@988204 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ColumnReference.java",
"hunks": [
{
"added": [
"",
" /**",
" * The FromTable this column reference is bound to.",
" */",
" private int tableNumber;",
"",
... |
derby-DERBY-4698-2e7e8f6d | DERBY-4698 Simple query with HAVING clause crashes with NullPointerException
Patch derby-4698-2. The case of column references in HAVING clauses
being wrong after JOIN flattening was initially solved by
DERBY-3880. That solution was partial in that it can sometimes happen
too late.
This patch changes the fix-up of column references in a having clause
after join flattening to the same point in time as that of other
column references that need fix-up after the flattening (rcl, column
references in join predicates and group by clauses). Thus the fixup is
moved from the modifyaccesspath phase to the preprocess phase.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@956234 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromList.java",
"hunks": [
{
"added": [
" * @param havingClause The HAVING clause, if any",
" GroupByList gbl,",
" ValueNode havingC... |
derby-DERBY-4699-a8132ce4 | DERBY-3989 / DERBY-4699
Made PropertySetter ignore Java 6 libraries if a Java 5 compiler is used.
If j16lib is specified explicitly in such an environment, the build will be
aborted (an error message will be displayed to the user).
Patch file: derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@954421 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyPreBuild/PropertySetter.java",
"hunks": [
{
"added": [
" if ( j14lib != null ) {",
" debug(\"'j14lib' explicitly set to '\" + j14lib + \"'\");",
" setClasspathFromLib(J14CLASSPATH, j14l... |
derby-DERBY-47-028077eb | DERBY-47 (partial): Patch to implement execution-time "probing" given a probe
predicate "place-holder" and a list of IN values. This patch creates a new
execution-time result, MuliProbeTableScanResultSet, to perform the probing.
At a higher-level the changes in this patch make it so that repeated calls to
MultiProbeTableScanResultSet.getNextRowCore() will first return all rows matching
probeValues[0], then all rows matching probeValues[1], and so on (duplicate probe
values are ignored). Once all matching rows for all values in probeValues have
been returned, the call to getNextRowCore() will return null, thereby ending
the scan.
In order to accommodate the above behavior, the following changes were made to
existing files:
1 - Add correct instantiation logic to the "getMultiProbeTableScanResultSet()"
method of GenericResultSetFactory, which was just a stub method before this
patch.
2 - Overloaded methods in TableScanResultSet to allow the passing of a "probe value"
into the openScanController() and reopenScanController() methods. The methods
then use the probe value (if one exists) as the start/stop key for positioning
a scan, instead of using the start/stop key passed into the result set constructor.
3 - Made the iapi.types.DataType class implement the java.lang.Comparable interface
for the sake of easy sorting (just let the JVM do the sort). Since DataType (the
superclass of all datatypes and base implementation of the DataValueDescriptor
interface) already has a "compare()" method that returns an integer to indicate
less than, greater than, or equal, all we have to do is wrap that method inside
a "compareTo()" method and we're done.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@517470 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/DataType.java",
"hunks": [
{
"added": [
"import java.lang.Comparable;"
],
"header": "@@ -35,6 +35,7 @@ import org.apache.derby.iapi.services.sanity.SanityManager;",
"removed": []
},
{
"adde... |
derby-DERBY-47-0b2eeba7 | DERBY-2491 (partial): Add new DistinctTest, not wired
in to _Suite due to one failing test case related to
DERBY-47 that merits investigation.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@523454 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/RuntimeStatisticsParser.java",
"hunks": [
{
"added": [
" private boolean distinctScan = false;",
" private boolean eliminatedDuplicates = false;",
" private boolean tableScan = false;",
" ... |
derby-DERBY-47-1ad3b32f | DERBY-47 (partial): First incremental patch for the multi-probing ("mp")
approach described in Jira comments. As mentioned in that comment, we need
to be able to distinguish between "true" relational predicates and "probe
predicates" so that we do not incorrectly perform certain operations on
probe predicates. This first patch adds the logic to allow such distinction.
In particular it:
- Adds a new method, "isRelationalOpPredicate()", to Predicate.java that
only returns true if the predicate is a "true" relational predicate; i.e.
it will return "false" for probe predicates.
- Updates several "if" statements in Predicate.java and PredicateList.java
to use the new method.
- Updates several utility methods in BinaryRelationalOperatorNode to distinguish
"true" relational operators from ones that are created internally for probe
predicates.
There should be no functional changes to Derby as a result of this patch.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@512079 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/BinaryRelationalOperatorNode.java",
"hunks": [
{
"added": [
"\t/* If this BinRelOp was created for an IN-list \"probe predicate\"",
"\t * then we keep a pointer to the original IN-list. This serves",
"\t * ... |
derby-DERBY-47-7777c5dd | DERBY-47 (partial): Patch that adds logic to create IN-list "probe predicates"
during preprocessing, thus allowing the code changes in all previous patches
for this issue to take effect. With this patch Derby will now re-write IN
lists as probe predicates and, if the optimizer thinks it is best to do so,
will do index "multi-probing" at execution time to avoid excessive scanning.
The changes in this patch affect "preprocessing" logic as follow:
1. Replaces "A" with "B", where "A" is existing logic that creates a BETWEEN
node for IN-lists containing all constants, and "B" is new logic that
creates a "probe predicate" for IN-lists containing all constants *and/or*
parameter nodes. The probe predicates are then used throughout optimization,
modification of access paths, code generation, and execution time (as
appropriate) in the manner described by previous patches for this issue.
2. Adds some additional logic to OrNode preprocessing to allow the conversion
of queries like:
select ... from T1 where i in (2, 3) or i in (7, 10)
into queries that look like:
select ... from T1 where i in (2, 3, 7, 10)
This is really just an extension of the existing logic to transform a
chain of OR nodes into an IN-list.
3. Adds logic to PredicateList.pushExpressionsIntoSelect() to correctly
copy "probe predicates" so that the left operand (column reference)
is pointing to the correct place when we do static pushing of one-
sided predicates (which is what a "probe predicate" is).
4. Adds a new method to ValueNodeList that is used for checking to see if
a list of IN values consists solely of constant and/or parameter nodes
(there are no other expressions or column references).
This patch also incorporates all of the test master updates required as a
result of the new multi-probing functionality.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@518322 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/InListOperatorNode.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.types.DataTypeDescriptor;"
],
"header": "@@ -31,6 +31,7 @@ import org.apache.derby.iapi.sql.dictionary.DataDictionary;",
"r... |
derby-DERBY-47-83802657 | DERBY-47 (partial): Update the logic for cost-based optimization (CBO) and
modification of access paths (MoAP) to recognize IN-list "probe predicates"
and to handle them appropriately. More specifically this patch adds code to
do the following:
- During costing, recognize when we're using a probe predicate as a
start/stop key and adjust the cost accordingly. This means multiplying
the estimated cost and row count for "column = ?" by the number of values
in the IN-list (because we are effectively going to evaluate "column = ?"
N times, where N is the size of the IN-list, and we could return one or
more rows for each of the N evaluations). We also want to make sure that
the resultant row count estimate is not greater than the total number of
rows in the table.
- When determining which predicates can be used as start/stop keys for the
current conglomerate, only consider a probe predicate to be a start/stop
key if it applies to the _first_ column in the conglomerate. Otherwise the
probe predicate would end up being generated as a store qualifier, which
means we would only get rows for which "column = ?" was true when the
parameter was set to the _first_ value in the IN-list. That means we would
end up with incorrect results (missing rows).
- If cost-based optimization is complete and we are modifying access paths
in preparation for code generation, then take any probe predicates that are
*not* going to be used as start/stop keys for the chosen conglomerate and
"revert" them back to the InListOperatorNodes from which they were built.
Those InListOpNodes will then be generated as normal IN-list restrictions
on the rows returned from store. If we did not do this reverting then the
predicates would ultimately be ignored (since they are not valid qualifiers)
and we would therefore end up with incorrect results (extra rows).
- If we're modifying access paths and we have chosen to do multi-probing of
an index then we disable bulk fetching for the target base table. Logically
this is not a requirement. However, it turns out that bulk fetch can lead
to poor performance when multi-probing an index if the number of probe
values is high (several hundred or more) BUT that number is still just a
small fraction of the total number of rows in the table. By disabling
bulk fetch for multi-probing we avoid this performance slowdown.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@513839 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromBaseTable.java",
"hunks": [
{
"added": [
"\t\t\t/* If we have a probe predicate that is being used as a start/stop",
"\t\t\t * key then ssKeySourceInList will hold the InListOperatorNode",
"\t\t\t * from... |
derby-DERBY-47-9d829130 | DERBY-47 (cleanup): Cleanup patch which does the following:
1 - Changes Predicate.isRelationalOpPredicate() so that it just calls
the already existing method "isRelationalOperator()" on the left
operand of the predicate's AND node. This ultimately comes down
to a simple check for a null variable in BinaryRelationalOperatorNode,
which is cheaper than the old check.
2 - Adds a new method, "isInListProbeNode()", to ValueNode. The default
case returns "false", while BinaryRelationalOperatorNode returns true
if it has a source IN-list associated with it.
Also adds a corresponding method called "isInListProbePredicate()"
to Predicate.java. This method allows for simple (and relatively
cheap) checking of a predicate to see if it is an IN-list probe
predicate.
3 - Modifies Predicate.getSourceInList() to return the underlying
InListOperatorNode for probe predicates AND for "normal"
IN-list predicates (i.e. an IN-list that could not be
transformed into a "probe predicate" because it contains
one or more non-parameter, non-constant values)
This then allowed for some cleanup of other related code in
PredicateList.java.
Also adds a second version of getSourceInList() that takes a
boolean argument; if true, then it will only return the source
IN list for a predicate *if* that predicate is an IN-list
probe predicate.
4 - Changes PredicateList.generateInListValues() to account for the
fact that it only ever gets called when we know that there is
a probe predicate in the list.
5 - Shortens a couple of lines in FromBaseTable that were added with
earlier patches but were longer than 80 chars. Also rewrites
one Sanity check in that class to avoid construction of strings
when no error occurs (per recent discussions on derby-dev).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@520188 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromBaseTable.java",
"hunks": [
{
"added": [
"\t\t\t\t\t * allow a single start/stop key per column position in",
"\t\t\t\t\t * the index (see PredicateList.orderUsefulPredicates()).",
"\t\t\t\t\t\tif ((ssKe... |
derby-DERBY-47-cbdc90cf | DERBY-47 (partial): Code generation patch that does the following:
1 - Moves the code for generating a list of IN values into a new method,
InListOperatorNode.generateListAsArray()". The new method is then called
from two places:
A. InListOperatorNode.generateExpression(): the "normal" code-path for
generating IN-list bytecode (prior to DERBY-47 changes).
B. PredicateList.generateInListValues(): new method for generating the IN-list
values that will serve as the execution-time index "probe" values. This
method also generates a boolean to indicate whether or not the values
are already sorted (i.e. if we sorted them at compile time, which means
they all must have been constants).
2 - Adds code to ParameterNode that allows generation of a "place-holder"
value (instead of the ParameterNode itself) for probe-predicates. This is
required because a probe predicate has the form "column = ?" where the right
operand is an internally generated parameter node that does not actually
correspond to a user parameter. Since that parameter node is "fake" we can't
really generate it; instead we need to be able to generate a legitimate
ValueNode--either a constant node or a "real" parameter node--to serve as
the place-holder.
3 - Updates the generateExpression() method of BinaryOperatorNode to account
for situations where the optimizer chooses a plan for which a probe pred is
*not* a useful start/stop key and thus is not being used for execution-time
index probing. In this case we simply "revert" the probe predicate back to
the InListOperatorNode from which it was created. Or put another way, we
"give up" on index multi-probing and simply generate the original IN-list
as a regular restriction. This patch also removes the now unnecessary
"revertToSourceInList()" calls from PredicateList.java.
4 - Adds logic to NestedLoopJoinStrategy to generate a new type of result set,
MultiProbeTableScanResultSet, for probing an index at execution time. The
new result set does not yet exist (incremental development) but the code to
generate such a result set is added as part of this patch.
5 - Adds a new method, "getMultiProbeTableScanResultSet()", to the
ResultSetFactory interface. Also adds a corresponding stub method to
GenericResultSetFactory. The latter is just a dummy method and will be
filled in with the appropriate code as part of a subsequent patch.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@515795 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/compile/JoinStrategy.java",
"hunks": [
{
"added": [
"\t * @param bulkFetch True means bulk fetch is being done on the inner table",
"\t * @param multiprobe True means we are probing the inner table for rows",
"\t * ... |
derby-DERBY-470-e1b8b606 | DERBY-470 - Exception when using LOCALIZEDDISPLAY with JSR169
1. Check for BigDecimal class in the JVM by doing a Class.forName
2. Call getNumberAsString for NUMERIC and DECIMAL types only if BigDecimal class is available. Otherwise, return rs.getString.
Contributed by Deepa Remesh
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@239718 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/iapi/tools/i18n/LocalizedResource.java",
"hunks": [
{
"added": [
"\tprivate static boolean HAVE_BIG_DECIMAL;",
"\t",
"\t{",
"\t\tboolean haveBigDecimal;",
"\t\ttry {",
"\t\t\tClass.forName(\"java... |
derby-DERBY-4700-43220cc1 | DERBY-4700: Add method to obtain a bogus port in TestConfiguration
Added the method getBogusPort to obtain a port where no Derby network server
is supposed to be running (i.e. when doing negative connect tests).
Patch file: derby-4700-1b.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@963705 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/TestConfiguration.java",
"hunks": [
{
"added": [
"public final class TestConfiguration {"
],
"header": "@@ -56,7 +56,7 @@ import junit.framework.TestSuite;",
"removed": [
"public class TestConfigu... |
derby-DERBY-4700-b765481f | DERBY-4700: Add method to obtain a bogus port in TestConfiguration
Made bogus port static so that it can be shared across TestConfiguration instances.
Increased the maximum port count to 20 (we're currently using 11 in suites.All).
Patch file: derby-4700-2a-static_bogus.diff
(changed 11 to 20 for MAX_PORTS_USED)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@964115 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/TestConfiguration.java",
"hunks": [
{
"added": [
" private final static int MAX_PORTS_USED = 20;",
" private static final int bogusPort;"
],
"header": "@@ -75,13 +75,14 @@ public final class TestCon... |
derby-DERBY-4704-0859d5b4 | DERBY-4704: Make casts of strings to booleans always nullable.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@956025 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4704-8260425f | DERBY-4704: Incorrect nullability when casting non-nullable VARCHAR to BOOLEAN
Added test case. Disabled for now.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@955900 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4706-ccfada30 | DERBY-4706: Remove stale and potentially unused code Request.writeEncryptedScalarStream
Removed the method writeEncryptedScalarStream in Request, and a number of methods only used by it. The other
methodsdiffer from their "normal" counter-parts only by writing into a new buffer instead of the transfer
buffer (i.e. typically because what's written has to be encoded before placed onto the transfer buffer).
Patch file: derby-4706-1a-remove_writeEncryptedScalarStream_and_friends.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@956569 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/Request.java",
"hunks": [
{
"added": [
" // DERBY-4706",
" // The network server doesn't support the security mechanisms above.",
" // Further, the code in writeEncryptedScalarStre... |
derby-DERBY-4709-155fa10b | DERBY-4709: Create test that parse client trace file to detect round-trips for Derby-4653.
Alternative test for commit/rollback flow optimization, which parses the
DRDA protocol flow log to verify that a commit/rollback flows over the network
only when required.
The test is very general, it does not test correct commit/rollback behavior for
specific database interaction sequences.
Patch file: derby-4709-1c-alternative_test.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@963243 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-471-8ff0b23f | DERBY-471 Correct DatabaseMetaData.getTimeDateFunctions to correctly return
a valid subset of the JDBC/ODBC escaped functions that Derby supports.
Expanded existing tests for time date functions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@348330 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-471-c84cf384 | DERBY-471 Correct DatabaseMetaData.getNumericFunctions,getSystemFunctions and getStringFunctions
to correctly return a valid subset of the JDBC/ODBC escaped functions that Derby supports.
Added tests that ensure the functions listed by Derby are supported, and that all
the functions defined by the spec and supported by Derby are listed by Derby.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@348289 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4711-780c0c3d | DERBY-4711: Hung thread after another thread is interrupted
If a thread fails while waiting for a lock, remove that thread from
the queue.
Patch contributed by Luke Quinane <luke@nuix.com>.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@957902 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/locks/LockSet.java",
"hunks": [
{
"added": [
" byte wakeupReason = 0;",
" try {",
" wakeupReason = waitingLock.waitForGrant(actualTimeout);",
"... |
derby-DERBY-4712-a823c6a8 | DERBY-4712 Complex nested joins problems
Patch DERBY-4712b, which removes one of the source for NPE seen by the reporter.
The other is covered by DERBY-4798.
A corner case: the patch makes an inner join which decides it is not
flattenable, propagate this fact down to any nested outer join nodes
containing nested inner joins, the latter inner joins will otherwise
think they are flattenable (a priori value for inner joins).
Adds new test cases.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@997325 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4713-70c969f3 | DERBY-4713; Subclasses of ScriptTestCase can not run correctly with the non-English default locale
committing patch derby-4713-2.
patch contributed by Yun Lee (yun dot lee dot bj at gmail dot com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1055998 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4715-6a108f11 | DERBY-4715 Write jvm information and path of derby.jar to derby.log
Contributed by Lily Wei (lily wei at yahoo dot com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@965647 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/BaseDataFileFactory.java",
"hunks": [
{
"added": [
"import java.io.UnsupportedEncodingException;",
"",
"import java.net.URL;",
"import java.net.URLDecoder;",
"import java.security.Code... |
derby-DERBY-4717-811c29d0 | DERBY-4717: Driver trace file isn't closed/released on physical connection close when specified with the traceFile attribute/setter
Made Derby close the trace file specified as 'traceFile' (data source setter or
as a connection URL attribute) when the physical connection is closed.
Patch file: derby-4717-1b.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@959550 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/jdbc/ClientBaseDataSource.java",
"hunks": [
{
"added": [
" if (printWriter != logWriter &&",
" (traceDirectory != null || traceFile != null))"
],
"header": "@@ -621,7 +621,8 @@ public abstract cla... |
derby-DERBY-4723-19311603 | DERBY-4723: Using an instance lock to protect static shared data in EmbedPooledConnection
Removed code using incorrect syncronization, as it was used for tracing only
and the hashCode() output should suffice for that.
Patch file: derby-4723-1a-remove_code.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@980089 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/jdbc/EmbedPooledConnection.java",
"hunks": [
{
"added": [],
"header": "@@ -64,13 +64,6 @@ import javax.sql.ConnectionEvent;",
"removed": [
"",
" /** Static counter for connection ids */",
" private stat... |
derby-DERBY-4729-eaa0d8cf | DERBY-4729 add more information to the XACT_PROTOCOL_VIOLATION returned from sto
re.
When this error is reported it is often hard to reproduce, so adding
printing of internal state of the Transaction when it is hit. Hopefully
this help in understanding what is going on when the error is hit.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1471079 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/xact/Xact.java",
"hunks": [
{
"added": [
" SQLState.XACT_PROTOCOL_VIOLATION_DETAILED, ",
" toInternalDetailString());"
],
"header": "@@ -757,7 +757,8 @@ public class... |
derby-DERBY-4730-1292a7f9 | DERBY-4730: Add BOOLEAN to list of datatypes returned by DatabaseMetaData.getTypeInfo().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@961497 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4731-2c70a31f | DERBY-4731 XA two phase commit with active GLOBAL TEMPORARY TABLE causes An internal error identified by RawStore module
For temp tables declared as following derby needs to do special work at the
time of commit to arrange for the temporary table to have no rows once the
commit completes.:
DECLARE GLOBAL TEMPORARY TABLE SESSION.T1 ( XWSID INT) ON COMMIT DELETE ROWS NOT LOGGED ON ROLLBACK DELETE ROWS
Derby implements these temporary tables as unlogged real internal tables with
backing containers on disk. The ddl is all in memory so that they are only
seen by the current session. On commit the underlying container is dropped and
a new empty container is created.
This all works fine except in the XA case. In this case the transaction
has done real updates (temp table updates are unlogged and thus not seen
as update operations from the XA point of view), then the transaction executes
an XA prepare followed by an XA commit. No update transactions are allowed
between the prepare and the commit. The problem is that the pre-commit work
done for the temp tables was executing updates on the internal containers
(dropping and createing new ones), and raw store identified this as an XA
protocol violation. Since the work is only on internal non XA transaction
related updates it is ok to do these between the prepare and commit.
The fix arranges for this work to be done in a nested updatable user transaction
when in an XA transaction. It is ok to commit this work independently from
the parent user transaction because
for XA because it does the right thing in both possible cases:
1) If the XA transaction commits successfully then the same work has been
done. Because of where it is done in the code, the committing user can
never get access to the global temp tables between the time the nested
xact commits and the XA transaction commits.
2) If the XA transaction fails to commit somehow, then I think one of two
things will happen:
a) the session will go away, and then it does not matter what happens
to the session life objects.
b) the transaction will rollback, and on commit work which deleted the
rows is the same work that needs to get done on rollback.
The only locks the nested transaction gets is created new containers, so there
should be no problem with lock contention of the work with either the parent
transaction, or any other transactions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@961511 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java",
"hunks": [
{
"added": [
" * Do the necessary work at commit time for temporary tables",
" * <p>",
" * 3)After savepoint fix up, then handle all ON COMMIT DELE... |
derby-DERBY-4731-2d08e7af | DERBY-4731
Previous change did not completely solve the problem. There is a problem with
the initial fix, not sure why it only showed an error in the 10.3 backport.
The temporary tables are stored in the transaction context, so using a nested
transaction creates a new context and the work there is not reflected in the
parent context. Thus the previous fix which used a nested transaction does
not work.
This patch delays the work on the XA global temporary tables until after the xa transaction has committed but before control returns to the client executing
the commit. The delay solves the issue of attempting to do work in a
prepared transaction.
It drops all global temporary tables following an XA commit. This gives us
consistent behavior between embedded and network server implementations. At
the time of an xa end the system "Ends the work performed on behalf of a transaction branch. The resource manager disassociates the XA resource from the transaction branch specified and lets the transaction complete." Given this
description of the behavior of XAResource it seems reasonable to document
that global temporary tables are not supported across the XA commit boundary.
In the worst case one might be connecting to an resource in completely another
database and the temp table implementation is tied to the transaction
context in a single connection to a existing server.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@965317 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java",
"hunks": [
{
"added": [
" ",
" for (int i=0; i<allDeclaredGlobalTempTables.size(); i++)",
" TableDescriptor td = ",
" ((... |
derby-DERBY-4731-3bb8c054 | DERBY-4731 XA two phase commit with active GLOBAL TEMPORARY TABLE causes An internal error identified by RawStore module
just checking in fixtures for the RawStore error and the the Assert case to XATest. The fixtures are xtestXATempTableD4731_RawStore() and xtestXATempTableD4731_Assert and can be enabled by removing the 'x' in front.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@960136 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4731-6819a865 | DERBY-4743 Attempt to access a DECLARE GLOBAL TEMPORARY TABLE after commit in an XA transaction in Network server fails.
The fix for DERBY-4731 made the behavior consistent across embedded and
network server. Derby does not support accessing global temporary tables
declared in an XA transaction subsequent to the commit of the transaction.
This change updates the junit XATest to verify that accessing the table after
the commit fails as expected in both the embedded and network server case. In
both cases you will get the generic table does not exist error.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@966027 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4732-52694e5d | DERBY-4732: Release system resources in CanonTestCase thoroughly
Added finally block to clean up resources.
Contributed by Yun Lee (yun dot lee dot bj at gmail dot com).
Patch file: derby-4732.patch
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@963716 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4735-452d4674 | DERBY-4735 prepare of an XA read only transaction with a declared global temporary table gets and ASSERT in SANE mode.
Fixing test case in the junit XATtest.java test. Changed it to not try and
do an xa commit after preparing a read only transaction. The test case still
gives an ASSERT, and in my run caused a subsequent error in the testDerby966
test, which I assume came from bad error processing of the ASSERT.
To enable test just remove the x from "public void xtestXATempTableD4735_Assert()"
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@966039 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4741-2c09e2c0 | DERBY-4741 Make embedded Derby work reliably in the presence of thread interrupts
Patch derby-4741-testBatchInterrupt-b:
It tests that an interrupt will stop a batch of statements by throwing
08000 just before we execute the next statement in the batch.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1066707 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4741-3a6f4cf9 | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Patch derby-4741-a-04-api-interruptstatus. This patch contains the new
helper class InterruptStatus and inserts calls to
restoreIntrFlagIfSeen in before API methods' return and in the
exception handling (TransactionResourceImpl#handleException).
In addition, execution of EmbedStatement#executeBatch checks for
interrupts between each statement in the batch and throws the
exisisting 08000 (CONN_INTERRUPT - session level severity) error if
interrupts are seen.
Note: Still, the machinery of InterruptStatus isn't really used to
save any interrupts, that follows in (a) later patch(es), so this
patch doesn't change behavior. The focus here is on the correct
placement of calls to restoreIntrFlagIfSeen in the API.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1030630 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/ConnectionChild.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.InterruptStatus;"
],
"header": "@@ -22,6 +22,7 @@",
"removed": []
}
]
},
{
"file": "java/engine/org/apache/der... |
derby-DERBY-4741-3abf75fd | DERBY-4741 Make embedded Derby work reliably in the presence of thread interrupts
Patch derby-4741-testQueryInterrupt.
* adds a new test case: InterruptResilienceTest#testLongQueryInterrupt
which tests that a query will check for the interrupt flag and throw
08000 (CONN_INTERRUPT) at the same time is checks for query
time-out.
* adds a missing piece of code in InterruptStatus#throwIf
* I also adjusted an existing test (for RAF recovery) to handle the
case that we could see 08000 (CONN_INTERRUPT) when performing a
query as part of that test, depending on when the interrupt happens.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1066701 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/util/InterruptStatus.java",
"hunks": [
{
"added": [
" * flag to allow safe operation during execution, or if the interrupt",
" * status flag is set now. Called when operations want to be prematurely",
" * t... |
derby-DERBY-4741-482ff80f | DERBY-4967 Handle interrupt received while waiting for database lock
Patch derby-4967-locking-4 which makes the existing test
LockInterruptTest assert that the interrupt flag is set when we see
08000 (CONN_INTERRUPT) - in accordance with the behavior we expect
after DERBY-4741. The assert is skipped on Solaris/Sun Java <= 1.6
unless the flag -XX:-UseVMInterruptibleIO is used.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1060832 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4741-5d974225 | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Patch derby-4741-sleeps-waits-3, which modifies all actions when
seeing interrupt in Object#wait and Thread#sleep inside
"org.apache.derby.impl.store.*" as well as in one other instance.
Thew new code just makes a note that an interrupt occured and then
retry. The old code sometimes threw 08000 (CONN_INTERRUPT) or just
ignored the interrupts.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1061516 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/GenericStatement.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.InterruptStatus;"
],
"header": "@@ -42,6 +42,7 @@ import org.apache.derby.iapi.sql.dictionary.SchemaDescriptor;",
"removed": []
... |
derby-DERBY-4741-616c0d01 | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Patch derby-4741-raf-stresstest-4. This patch adds a new test fixture to
InterruptResilienceTest: multi-threaded read/write test under an interrupt
shower. This exercises primarily the random access file recovery
(RAFContainer4#recoverContainerAfterInterrupt), but since the interrupt can
arrive at any time during query execution, higher levels of the embedded code
are also exposed (jdbc, language, store).
The new test case is InterruptResilienceTest#testRAFReadWriteMultipleThreads.
I also found I had to add Class.forName(<driver>) to
DriverManagerConnector#getConnectionByAttributes and a new public method
BasicJDBCTestCase#openDefaultConnection(TestConfiguration). The latter makes it
possible use the main thread's test configuration in the server threads (when
runnin the test in client-server mode), cf. "thisConfig" member in
InterruptResilienceTest.
The test now runs in its own database, with derby.system.durability=test for
speed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1064174 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer4.java",
"hunks": [
{
"added": [
" // Interrupt recovery \"stealthMode\": If this thread holds a monitor on",
" //",
" // a) \"this\" (when RAFContainer#clean calls getE... |
derby-DERBY-4741-794fc707 | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Added missing copyright header to the newly introduced class InterruptStatus.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1030814 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/util/InterruptStatus.java",
"hunks": [
{
"added": [
"/*",
"",
" Derby - Class org.apache.derby.iapi.util.InterruptStatus",
"",
" Licensed to the Apache Software Foundation (ASF) under one or more... |
derby-DERBY-4741-b231544c | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Patch derby-4741-kristians-01, incorporating Kristian's comments. Should not change behavior.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1043802 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer4.java",
"hunks": [
{
"added": [
" private final Object channelCleanupMonitor = new Object();"
],
"header": "@@ -79,7 +79,7 @@ class RAFContainer4 extends RAFContainer {",
"removed": [
... |
derby-DERBY-4741-bd018fd9 | DERBY-4741 Make Derby work reliably in the presence of thread interrupts
Patch derby-4741-c-01-nio: closes two corner cases I have
observed when stress testing the RAFContainer4 recovery mechanism. It
also does some other small cleanups. Regressions ran OK.
RAFContainer:
If we receive an interrupt when the container is first being opened
(i.e. during RAFContainer.run (OPEN_CONTAINER_ACTION) ->
getEmbryonicPage), recovery will fail because currentIdentity needed
in RAFContainer4#recoverContainerAfterInterrupt hasn't yet been
set.
RAFContainer4:
If a stealthMode read is interrupted and is recovering the container,
it erroneously increments threadsInPageIO just before exiting to retry
IO. This leads to a break in the invariant that threadsInPageIO be 0
when all threads are done, causing issue (hang) down the line.
If, when we are reopening the container, the read being done during
that operation (getEmbryonicPage), that stealth mode read will also
lead to a (recursive) recovery. We have to catch this case by adding a
"catch (InterruptDetectedException e)" just after the call to
openContainer, not by testing the interrupt flag as presently done,
since the recovery inside the recursive call to
getEmbryonicPage/readPage will already have cleared the flag and done
recovery.
When giving up reopening the container for some reason, we also forgot
to decrement threadsInPageIO.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1040086 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer.java",
"hunks": [
{
"added": [
" protected ContainerKey idAPriori = null;",
"",
" synchronized boolean openContainer(ContainerKey newIdentity)",
" boolean success = fal... |
derby-DERBY-4741-c9528432 | DERBY-4769 Handle interrupt received while waiting for database lock
(subtask of DERBY-4741): Patch derby-4967-locking-1 which lets Derby
throw CONN_INTERRUPT if an interrupt is received while waiting for a
database lock.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1058245 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/locks/LockSet.java",
"hunks": [
{
"added": [
" // If we were not woken by another then we have timed",
" // out. Either deadlock out or timeout. Or thread has",
" ... |
derby-DERBY-4741-ec9d167b | DERBY-4741 Make embedded Derby work reliably in the presence of thread interrupts
Patch derby-4741-sleeps-waits-more, which "regularizes" a few more
instances of interrrupt handling to follow the idiom established in
this issue's patches.
This leaves a few instances in BasicDaemon.java (as far as embedded
code is concerned), which will need more consideration. In any case,
interrupting the demon threads is less of a valid use case I believe,
i.e. Derby's ability to tolerate that is less crucial that tolerating
interrupts to the user's connection threads.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1073595 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/db/SlaveDatabase.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.util.InterruptStatus;"
],
"header": "@@ -30,6 +30,7 @@ import org.apache.derby.iapi.jdbc.AuthenticationService;",
"removed": []
},
... |
derby-DERBY-4743-6819a865 | DERBY-4743 Attempt to access a DECLARE GLOBAL TEMPORARY TABLE after commit in an XA transaction in Network server fails.
The fix for DERBY-4731 made the behavior consistent across embedded and
network server. Derby does not support accessing global temporary tables
declared in an XA transaction subsequent to the commit of the transaction.
This change updates the junit XATest to verify that accessing the table after
the commit fails as expected in both the embedded and network server case. In
both cases you will get the generic table does not exist error.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@966027 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4743-af45571f | DERBY-4743
Checking in changes to XATest.java to repro this bug. The test case is currently
disabled. To enable it remove the x from:
public void xtestXATempTableD4743()
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@963931 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4748-7b374f98 | DERBY-4748: StringIndexOutOfBoundsException on syntax error (invalid COMMIT)
Rewrote logic in isolateAnyInitialIdentifier and added test case.
Patch contributed by Knut Anders Hatlen (knut dot hatlen at oracle dot com) and
Kristian Waagan (kristwaa at apache dot org).
Patch file: derby-4748-1b-sioobe.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@980684 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-475-14d5f009 | DERBY-475 Add a table driven mechanism to allow simple one argument
functions to be added easily. These functions exist only at runtime
in the SYSFUN schema and are resolved to with an explicit use of SYSFUN
or an unqualified functon name. Start off with a set of stanadard
functions from the java.lang.Math class.
git-svn-id: https://svn.apache.org/repos/asf/incubator/derby/code/trunk@226528 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/types/RoutineAliasInfo.java",
"hunks": [
{
"added": [],
"header": "@@ -122,7 +122,6 @@ public class RoutineAliasInfo extends MethodAliasInfo",
"removed": [
"\t\tsetAliasType();"
]
},
{
"added"... |
derby-DERBY-475-b7e5031d | DERBY-475 DERBY-592 Expand the builtin function table to handle zero parameter
functions and add the functions PI and LOG10 as builting and JDBC escaped functions.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@374471 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/SystemProcedures.java",
"hunks": [
{
"added": [
"\t",
"\t<P>",
"\tAlso used for builtin-routines, such as SYSFUN functions, when direct calls",
"\tinto Java libraries cannot be made."
],
"he... |
derby-DERBY-4752-49174a90 | DERBY-4752: CheapDateFormatter returns incorrect and invalid date strings
Use java.util.Calendar to get the calculations right.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@967000 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/util/CheapDateFormatter.java",
"hunks": [
{
"added": [
"import java.util.Calendar;",
"import java.util.Locale;",
"import java.util.TimeZone;",
"",
" private static final TimeZone GMT = TimeZone.ge... |
derby-DERBY-4752-6500326f | DERBY-4752: CheapDateFormatter returns incorrect and invalid date strings
Removed the CheapDateFormatter class and made the code use
java.util.Date and its toString() method instead.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@988874 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"import java.util.Date;"
],
"header": "@@ -53,6 +53,7 @@ import java.sql.DriverManager;",
"removed": []
},
{
"added": [],
"heade... |
derby-DERBY-4753-7b6ad6da | DERBY-4753: "ERROR 42X01: Syntax error: FALSE." during call to java.sql.DatabaseMetaData.getIndexInfo
When recompiling a meta-data query after detecting that its plan is
stale, pass down a flag to the compiler to say that it's a meta-data
query and that use of internal syntax is allowed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1570490 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/PreparedStatement.java",
"hunks": [
{
"added": [
" * @param forMetaData true if this is a meta-data query"
],
"header": "@@ -102,6 +102,7 @@ public interface PreparedStatement",
"removed": []
}
]
... |
derby-DERBY-4754-a2a0ff24 | DERBY-4754: Make the getObject() methods of Derby's LOBs always return jdbc LOBs.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@982585 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/SQLClob.java",
"hunks": [
{
"added": [
" /**",
" * @exception StandardException Thrown on error",
" */",
" public Object getObject() throws StandardException",
" {",
... |
derby-DERBY-4764-782dbe17 | DERBY-4764: Files with missing ASF license headers
Added or modified Apache license headers where missing or old.
Patch file: derby-4764-1a-license_headers_trunk.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@984922 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/tools/PlanExporter.java",
"hunks": [
{
"added": [
"/*",
"",
" Derby - Class org.apache.derby.tools.PlanExporter",
"",
" Licensed to the Apache Software Foundation (ASF) under one or more",
" ... |
derby-DERBY-4767-4eeab6ca | DERBY-4767; Detailed prompt for Error CSL16 is different between Client and Embedded
adding a check for the value of the operation, and fixing up some areas where an incorrect operation value was passed on.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@986145 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ResultSet.java",
"hunks": [
{
"added": [
" return getBoolean(findColumnX(columnName, \"getBoolean\"));"
],
"header": "@@ -1440,7 +1440,7 @@ public abstract class ResultSet implements java.sql.ResultSet,",
... |
derby-DERBY-4767-c9687fc4 | DERBY-4767; Detailed prompt for Error XCL16 is different between Client and Embedded
patch contributed by Yun Lee (yun dot lee dot bj at gmail dot com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@985550 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ResultSet.java",
"hunks": [
{
"added": [
" checkForClosedResultSet(\"next\");"
],
"header": "@@ -293,7 +293,7 @@ public abstract class ResultSet implements java.sql.ResultSet,",
"removed": [
" ... |
derby-DERBY-4769-c9528432 | DERBY-4769 Handle interrupt received while waiting for database lock
(subtask of DERBY-4741): Patch derby-4967-locking-1 which lets Derby
throw CONN_INTERRUPT if an interrupt is received while waiting for a
database lock.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1058245 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/locks/LockSet.java",
"hunks": [
{
"added": [
" // If we were not woken by another then we have timed",
" // out. Either deadlock out or timeout. Or thread has",
" ... |
derby-DERBY-4771-174db5a9 | DERBY-4771: Continue investigation of automatic creation/update of index statistics.
Removed unused method getRowEstimate.
Spotted by Dag H. Wanvik (dag dot wanvik at oracle dot com).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1042461 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/QueryTreeNode.java",
"hunks": [
{
"added": [],
"header": "@@ -579,23 +579,6 @@ public abstract class QueryTreeNode implements Visitable",
"removed": [
"\t/**",
"\t * Get the optimizer's estimate of the... |
derby-DERBY-4772-4771f1f4 | DERBY-4772: Data truncation error with XPLAIN-functionality enabled
Increased max length of string fields with undefined max lenghts to the
maximum allowed length of the VARCHAR data type (and also changed the data
type from CHAR to VARCHAR).
Patch file: derby-4772-1b-increase_max_len.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1033864 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/XPLAINResultSetDescriptor.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.types.TypeId;"
],
"header": "@@ -26,7 +26,7 @@ import java.sql.SQLException;",
"removed": [
"import org.ap... |
derby-DERBY-4772-f1c83832 | DERBY-4772 (cleanup): Data truncation error with XPLAIN-functionality enabled
Cleaned up a bunch of unused imports, some unused variables and removed an
Exception.printStackTrace().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1027921 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/xplain/XPLAINSystemTableVisitor.java",
"hunks": [
{
"added": [],
"header": "@@ -28,22 +28,15 @@ import java.sql.Timestamp;",
"removed": [
"import java.util.Properties;",
"import org.apache.derby.jdbc.I... |
derby-DERBY-4779-d9a720b2 | DERBY-4779: Commit patch contributed by Siddharth Srivastava which eliminates an NPE caused by the interaction of generated columns and triggers.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1140222 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4781-11ab591f | DERBY-4781 suites.All fails completely with Failed to invoke suite():java.lang.reflect.InvocationTargetException because of XplainStatisticsTest
Change getADocument() to return an Object instead of Document so weme does not fail to load the class.
Contributed by Knut Anders Hatlen
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@988321 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4781-158ccc5d | DERBY-4781: suites.All fails completely with Failed to invoke suite():java.lang.reflect.InvocationTargetException because of XplainStatisticsTest
Fixed replace() method. The old version would sometimes erroneously
return an empty string.
Patch contributed by Nirmal Fernando <nirmal070125@gmail.com>.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@989036 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/planexporter/AccessDatabase.java",
"hunks": [
{
"added": [
" \t int idx = stmt.indexOf(expr);",
" \t while (idx >= 0)",
" \t {",
" \t stmt = stmt.substring(0, idx) + replace + stmt.substring... |
derby-DERBY-4781-b1b255cc | DERBY-4781 (partial) Fix XplainStatisticsTest failure with J2ME on split method
introduced by DERBY-4587
Contributed by C.S. Nirmal J Fernando ( nirmal070125 at gmail dot com )
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@988264 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/planexporter/AccessDatabase.java",
"hunks": [
{
"added": [
" \tif(stmt.indexOf(expr)!=-1){",
" \t\tstmt=stmt.substring(0, stmt.indexOf(expr))",
" \t\t+replace+stmt.substring(stmt.indexOf(expr)+1);",
... |
derby-DERBY-4786-04243ad4 | DERBY-4786 (Shutdown command without username and password should work with mixed client and network server releases.)
This change will send shutdown command with protocol level 2 whether there is username or password provided or not. If this command fails because of DRDA_InvalidReplyHead from server, then it will resend the shutdown command but this time with protocol level 1. The attempt with protocol level 1 will be made only if there was no username and password supplied with the shutdown command because shutdown command at protocol level 1 does not support username/password.
If a client with these changes sends a shutdown command to a 10.3 server(which does not have DERBY-2109 changes) without the username and password, it will get 2 exceptions back from the server. 1st exception will be for sending the shutdown command at protocol level 2 and the 2nd will be for shutting down the server succesfully. Server will also have 2 messages, first indicating that an invalid protocol level command was received and 2nd message saying that the server is shutdown. I will create a release note for this behavior.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@999119 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"\t//All the commands except shutdown with username and password are at ",
"\t//protocol level 1. ",
"\tprivate final static int DEFAULT_PROTOCOL_VERSION = 1;",... |
derby-DERBY-4789-66f38fa6 | DERBY-4789 Add more tests for bulk insert on self join, union, left outer join and expected results.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@996700 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4789-d7ee7fac | DERBY-4789: Attempt bulk-insert optimization when inserting from a table function.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@993374 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-479-3905037d | DERBY-479 Fix linkage error when passing the value of a RETURNS NULL ON NULL INPUT function
to another function. Fixed by only removing SQLToJava/JavaToSQL nodes for the function's
return value when the function is a CALLED ON NULL INPUT function.
Fix contributed by Mamta Satoor - msatoor@gmail.com
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@381553 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/MethodCallNode.java",
"hunks": [
{
"added": [
"\t\t\t** Since we need the parameter to be in Java domain format, put a",
"\t\t\t** SQLToJavaValueNode on top of the parameter node if it is a ",
"\t\t\t** SQLV... |
derby-DERBY-4791-19984411 | DERBY-4791 (partial) LIKE operator optimizations and concatenation
Made ConcatenationOperatorNode capable of constant folding so that for
example 'ab' || '%' can be handled the same way as 'ab%'.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@993074 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ConcatenationOperatorNode.java",
"hunks": [
{
"added": [
" /**",
" * Check if this node always evaluates to the same value. If so, return",
" * a constant node representing the known result.",
... |
derby-DERBY-4798-a823c6a8 | DERBY-4712 Complex nested joins problems
Patch DERBY-4712b, which removes one of the source for NPE seen by the reporter.
The other is covered by DERBY-4798.
A corner case: the patch makes an inner join which decides it is not
flattenable, propagate this fact down to any nested outer join nodes
containing nested inner joins, the latter inner joins will otherwise
think they are flattenable (a priori value for inner joins).
Adds new test cases.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@997325 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4798-d9dd1e59 | DERBY-4798 NPE in nested outer join
Patch derby-4798a.
Reintroduces the bailout code in BaseActivation#getColumnFromRow which
was removed in DERBY-3097 until we understand why it is needed.
Adds the repro for this issue to OuterJoinTest
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@998170 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-48-4d8deb63 | DERBY-48 A connection request that has a default schema that is being created by another transaction will fail to connect
Patch derby-48-7, which auto-creates the schema in a nested transaction if possible, thus
allowing early release of write locks used to auto-create the schema.
This has the side-effect of making auto-created schema persist even if
the user transaction that triggered it rolls back. Added a new test.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@662446 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
"\t\t\t\t\t\tfalse,",
"\t\t\t\t\t\ttc);"
],
"header": "@@ -1522,7 +1522,8 @@ public final class\tDataDictionaryImpl",
"removed": [
"\... |
derby-DERBY-48-9e04f690 | DERBY-48 A connection request that has a default schema that is being created by another transaction will fail to connect
Patch derby-48b, which limits the use of a subtransaction to the
initial default schema, other implicit schema creation is
transactional. A new testcase is added to show the latter.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@685141 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-48-ddae94a2 | DERBY-48 A connection request that has a default schema that is being created by another transaction will fail to connect
Follow-up patch to svn 685141, which accidentally committed the wrong patch revision.
With this patch, the net effect is DERBY-48b-1 which should have been committed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@685232 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/DDLConstantAction.java",
"hunks": [
{
"added": [
"\t\t\tCreateSchemaConstantAction csca",
"\t\t\t\t= new CreateSchemaConstantAction(schemaName, (String) null);",
"\t\t\t\t// DERBY-48: This operation creates ... |
derby-DERBY-4803-30dd4c58 | DERBY-4803: Make it possible to use sequences in INSERT...SELECT statements.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@999908 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4804-0d6a26d8 | DERBY-4804: Make database used in store.OSReadOnlyTest fully read-only
Properly simulate a read-only media.
Since Java cannot make a file writeable after first making it read-only until
Java SE 6, the db.lck file (with invalid contents) was created and made
read-only instead.
Patch file: derby-4804-1a-test_change.diff (modified some comments)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@998844 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4804-c7b35898 | DERBY-4804: Make database used in store.OSReadOnlyTest fully read-only
Followup patch moving file operation code into PrivilegedFileOpsForTests,
since it is probably useful for other tests as well.
Also note the new assert-method in BaseJDBCTestCase, used to assert that a
directory is fully deleted.
Patch file: derby-4804-2a-common_file_ops.diff
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@999796 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-4805-813aa38e | DERBY-4805(Increase the length of the RDBNAM field in the DRDA implementation)
This commit will allow RDBNAM to be 1024 bytes, thus lifting the limit from current 255bytes. I have changed the existing boundary test case to test for the new limit but the tests now use in-memory db jdbc url since on disk long urls were running into problem because of OS/file system limitation on the length of file name length.
As for newer client(version 10.11 and higher) going against an older server(10.10 and lower which will not have the fix for DERBY-4805 and hence will not accept the longer RDBNAM) with new RDBNAM limit, it will result in protocol exception. This is because when the client makes the first connect request to server, it has no way of knowing what server version it is talking to and hence there is no way to catch the length violation on the client side at this point.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1565491 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ClientDatabaseMetaData.java",
"hunks": [
{
"added": [
" /**",
" * DERBY-4805(Increase the length of the RDBNAM field in the DRDA ",
" * implementation) ",
" * True if the server supports... |
derby-DERBY-4806-7a7a289e | DERBY-4806 DERBY-4597 removes references to IBM jcc driver on Main.java, fixing extracting derbyTesting.jar information when it is not in the same directory as derbyrun.jar
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1002682 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/sysinfo/Main.java",
"hunks": [
{
"added": [
""
],
"header": "@@ -139,9 +139,9 @@ public static void getMainInfo (java.io.PrintWriter aw, boolean pause) {",
"removed": [
""
]
},
{
... |
derby-DERBY-4808-ce433402 | DERBY-4808; write a test that checks that optional packages are in place and clearly exposes when this is not the case
Adding some more checks to the EnvTest, plus modifying output mechanism
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1603557 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-481-15b837ec | DERBY-481: Cleanup based on comments from Dag and Knut.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@719760 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/DMLModStatementNode.java",
"hunks": [
{
"added": [
" *",
" * @param targetRCL the row in the table being INSERTed or UPDATEd",
" * @param forUpdate true if this is an UPDATE. false otherwise.",... |
derby-DERBY-481-291f9137 | DERBY-481: Add tests for altering the datatype of generated columns and of the columns they depend on.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@711663 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-481-2a0827ac | DERBY-481: Forbid generation clauses which reference generated columns.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@709219 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/CreateTableNode.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.services.io.FormatableBitSet;"
],
"header": "@@ -25,6 +25,7 @@ import org.apache.derby.iapi.reference.Property;",
"removed": [... |
derby-DERBY-481-3c09be76 | DERBY-481: Prevent users from dropping a function mentioned in a generation clause.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@712840 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/TableElementList.java",
"hunks": [
{
"added": [
"\tpublic int genColumnInfos( ColumnInfo[] colInfos)",
" throws StandardException"
],
"header": "@@ -430,7 +430,8 @@ public class TableElementList... |
derby-DERBY-481-45c66917 | DERBY-481: Add tests to verify that you can't use updatable ResultSets to corrupt generated columns.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@719656 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-481-4e6df7ab | DERBY-481: Incorporate Dag's patch review feedback.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@722214 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/NoRowsResultSetImpl.java",
"hunks": [
{
"added": [
" private int firstColumn = -1; // First column being stuffed. For UPDATES, this lies in the second half of the row.",
" private ... |
derby-DERBY-481-5a0cfa25 | DERBY-481: Generation clauses may not invoke functions which run SQL.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@709415 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/compile/CompilerContext.java",
"hunks": [
{
"added": [
"\tpublic static final int\t\t\tSQL_IN_ROUTINES_ILLEGAL\t\t=\t0x00002000;"
],
"header": "@@ -100,6 +100,7 @@ public interface CompilerContext extends Context",
... |
derby-DERBY-481-7101c06c | DERBY-481: Add negative test cases for generation clauses which mention CURRENT SCHEMA and CURRENT SQLID.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@714188 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-481-9188c1cc | DERBY-481: Catalog changes supporting generated columns.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@707414 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/DefaultInfo.java",
"hunks": [
{
"added": [
"\t/**",
"\t * If this default is a generation clause, then return the 1-based ids of",
"\t * other columns in the row which the generation clause references.",
"\... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.