id stringlengths 22 25 | commit_message stringlengths 137 6.96k | diffs listlengths 0 63 |
|---|---|---|
derby-DERBY-1357-450df233 | DERBY-1357: Fix optimizer short-circuit logic. Here is the note from the contributor.
I also had to update the lang/predicatePushdown.out master file because with the d1357_v1.patch the order of a couple of qualifiers has changed. Note that the query plans themselves are exactly the same--the only thing that's changed is the the qualifier ordering for one query. This change of order occurs because as part of the costing code in FromBaseTable.estimateCost() the optimizer transfers predicates from one predicate list to another, gets an estimated cost, then puts the predicates back into the original list. The methods to do this transferring are in NestedLoopJoinStrategy.java and HashJoinStrategy.java. In the former, the predicates are transferred away in front-to-back order and then transferred back in back-to-front order, which leads to a reversal of the relevant predicate ordering. Ex. If we have a list L1 of preds A,B,C and we transfer them to L2 in front-to-back order, L2 will end up with A,B,C. Then, when we transfer the predicates back to L1, if we process L2 in back-to-front order, L1 will end up with C,B,A. That said, with d1357_v1 applied the short-circuit logic prevents the optimizer from trying to optimize a join order that is known to be bad. This means that we skip an unnecessary round of optimization and therefore skip one round of order reversal, which means the order of the predicate qualifiers in the final plan is now different.
I ran derbyall on Red Hat with sane jars and ibm142, and saw no new failures.
Submitted by Army Brown (qozinx@gmail.com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@423754 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/OptimizerImpl.java",
"hunks": [
{
"added": [
"",
"\t\t/* Determine if the current plan is still less expensive than",
"\t\t * the best plan so far. If bestCost is uninitialized then",
"\t\t * we w... |
derby-DERBY-1361-9634cd20 | DERBY-1361 positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@417366 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1364-d8383bd9 | DERBY-1364: Client driver does not roll back the effects of a stored
procedure when incorrectly invoked by executeQuery()/executeUpdate()
Description of the patch:
1. Checking of the number of result sets returned was moved from
executeUpdate/executeQuery to a point in flowExecute where the
transaction has not been auto-committed (otherwise, the transaction
would already be committed when the exception was raised).
2. If the number of result sets does not match the execute type and
auto-commit is enabled, the transaction is rolled back (otherwise,
the transaction would be committed when the Statement was closed or
re-executed).
3. All execute* methods in CallableStatement were removed since they
have become identical to the methods in PreparedStatement. (Or
almost identical. The methods in CallableStatement did not call
checkStatementValidity() on errors, but that's probably a bug.)
4. SQL state for error message in executeQuery() was changed to match
embedded (XJ201/XJ205 -> X0Y78). Updated English and Portuguese
messages to use the new SQL state (no other translations existed
for XJ201 and XJ205).
5. Added more rollback tests to jdbcapi/ProcedureTest.junit and
enabled all test cases for DerbyNetClient.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@418692 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/CallableStatement.java",
"hunks": [
{
"added": [],
"header": "@@ -127,89 +127,6 @@ public class CallableStatement extends PreparedStatement",
"removed": [
" public boolean execute() throws SQLException {",
... |
derby-DERBY-1364-fade7e97 | DERBY-501: Client and embedded drivers differ on invoking a procedure
that returns a single Dynamic resultSet using CallableStatement.executeQuery()
This patch modifies EmbedStatement.processDynamicResults() so that it
returns the number of dynamic results instead of a
boolean. EmbedStatement.executeStatement() uses this number to decide
whether an exception is to be raised. With this change, the
executeQuery and executeUpdate parameters are no longer needed in
GenericPreparedStatement.execute().
ProcedureTest.junit is now enabled in derbyall (all frameworks). Seven
of the test cases run in the embedded framework only, but I expect all
of them to succeed with the client driver after DERBY-1314 and
DERBY-1364 have been fixed.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@414795 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/PreparedStatement.java",
"hunks": [
{
"added": [],
"header": "@@ -101,8 +101,6 @@ public interface PreparedStatement",
"removed": [
"\t * @param executeQuery\t\tWhether or not called from a Statement.executeQuery()",
... |
derby-DERBY-1365-985a9b0b | DERBY-1365: Fixes two minor problems with logic in Optimizer. Here is the note from contributor:
In addition to fixing the two issues described, the patch also resolves another potential problem: there are several places in OptimizerImpl.getNextPermutation() where calls to rewindJoinOrder() are made. These calls typically indicate that the optimizer has decided to abandon or "short circuit" a join order before calculating the full cost. For some of these calls--esp. the ones that can occur in the middle of the join order (as opposed to those which will only occur on a complete join order)--the "rewind" operation needs to make sure to reload the best plans for the optimizables that are pulled as part of the "rewind" process. Otherwise Derby could end up generating a plan for an optimizable even though that plan was part of a join order that was "abandoned" (i.e. rewound in the middle), which is logically incorrect and could lead to sub-optimal performance. I've included changes for this issue as part of d1365_v1.patch.
I ran derbyall on Red Hat Linux with d1365_v1.patch applied and saw no new failures. I would appreciate reviews/comments/commit if anyone has the time...
Submitted by Army Brown (qozinx@gmail.com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@412222 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/store/access/BackingStoreHashtable.java",
"hunks": [
{
"added": [
" // Check to see how much memory we think the first row"
],
"header": "@@ -273,7 +273,7 @@ public class BackingStoreHashtable",
"... |
derby-DERBY-1367-0400f845 | DERBY-1367: Enable grantRevoke.java test in DerbyNetClient framework.
Submitted by Satheesh Bandaram (satheesh@gmail.com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@427358 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1368-47cbf26e | DERBY-1368 EOFException when reading from blob's binary stream
This patch just adds a test. Bug was fixed previously with 10.2. I am not sure exactly which checkin fixed it.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@610094 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-137-9f5e1d4a | DERBY-137: Derby metadata always returns JDBC 2 result sets, even when
JDBC 3 result sets are required.
Summary of the changes:
DatabaseMetaData:
- getProcedureColumns: modified VTI to return an int instead of a
short for the DATA_TYPE column
- getTables: new columns: TYPE_CAT, TYPE_SCHEM, TYPE_NAME,
SELF_REFERENCING_COL_NAME, REF_GENERATION (all null since Derby
doesn't support typed tables)
- getColumns: DATA_TYPE changed from SMALLINT to INTEGER. New
columns: SCOPE_CATLOG, SCOPE_SCHEMA, SCOPE_TABLE,
SOURCE_DATATYPE (all null since Derby doesn't support the REF or
DISTINCT data types)
- getVersionColumns: SCOPE, DECIMAL_DIGITS and PSEUDO_COLUMN
changed from INTEGER to SMALLINT
- getPrimaryKeys: KEY_SEQ changed from INTEGER to SMALLINT (the
new query is ODBC compliant so getPrimaryKeysForODBC was removed)
- getTypeInfo: DATA_TYPE changed from SMALLINT to INTEGER, NULLABLE,
SEARCHABLE, MINIMUM_SCALE and MAXIMUM_SCALE changed from INTEGER to
SMALLINT
- getIndexInfo: ORDINAL_POSITION changed from INTEGER to SMALLINT
- getBestRowIdentifier: DATA_TYPE changed from SMALLINT to INTEGER
- getUDTs: new columm: BASE_TYPE (null since Derby doesn't support
the DISTINCT type or SELF_REFERENCING_COLUMN)
ODBCMetadataGenerator:
- cast DATA_TYPE columns to SMALLINT (as defined by ODBC)
- don't cast columns that already are SMALLINT to SMALLINT
Tests:
- updated master files for metadata, odbc_metadata,
bestrowidentifier, declareGlobalTempTableJava and
Upgrade_10_1_10_2 (new columns and modified data types)
- odbc_metadata.java: added information about nullability for some
of the new columns to avoid ArrayIndexOutOfBoundsException
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@417497 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyBuild/ODBCMetadataGenerator.java",
"hunks": [
{
"added": [],
"header": "@@ -202,9 +202,6 @@ public class ODBCMetadataGenerator {",
"removed": [
"\t\tchangeMap.put(\"getPrimaryKeys\",",
"\t\t\tnew Byte(TYPE_VALUE_CHANGE))... |
derby-DERBY-1373-97cac2ed | DERBY-1373: Encrypted databases cannot be booted using the jar subprotocol
Patch Contributed by Sunitha Kambhampati.
This patch makes the following changes:
1) Instead of using RandomAccessFile, the verifyKey.dat is read
as a InputStream.
2) Add a new test (encryptionKey_jar.sql) for booting encrypted
database using encryptionKey via classpath, and jar subprotocol.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@423682 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/jce/JCECipherFactory.java",
"hunks": [
{
"added": [
"import java.io.InputStream;",
"import java.io.DataInputStream;"
],
"header": "@@ -48,6 +48,8 @@ import java.security.spec.KeySpec;",
"removed":... |
derby-DERBY-1374-4d34a234 | DERBY-1374 compatibility test fails with PROTOCOL Data Stream Syntax Error.Patch contributed by Fernanda Pizzorno
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@415557 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetConnectionRequest.java",
"hunks": [
{
"added": [],
"header": "@@ -395,9 +395,6 @@ public class NetConnectionRequest extends Request implements ConnectionRequestIn",
"removed": [
" // This specifies the SQL E... |
derby-DERBY-1377-0cc1b092 | DERBY-1377: (Partial) - Dag's changes to sql/execute/rts
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429839 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/rts/RunTimeStatisticsImpl.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
"... |
derby-DERBY-1377-11bc2d08 | DERBY-1377: (Partial). Inserted license headers to .jj files
and updated java files for the tools/ij subdirectory.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429500 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/ij/xaHelper.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for addi... |
derby-DERBY-1377-15651f53 | DERBY-1377 (partial): update license headers on functionTests files outside of
the tests directory.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429889 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/util/metadataHelperProcs.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
... |
derby-DERBY-1377-1d8e53f6 | DERBY-1377: (Partial) - Dag's mods to iapi/error
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429922 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/error/StandardException.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work f... |
derby-DERBY-1377-20cdca37 | DERBY-1377 (Partial) - Fix license headers for the dblook subdirectory.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429734 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/dblook/Logs.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for addi... |
derby-DERBY-1377-22c1b9ca | DERBY-1377: (partial) - Dag's changes for sql/depend
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429830 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/depend/DepClassInfo.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work f... |
derby-DERBY-1377-23683f1d | DERBY-1377 (partial): update license headers for plugins subdirectory.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429773 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "plugins/eclipse/org.apache.derby.ui/src/org/apache/derby/ui/popup/actions/AddDerbyNature.java",
"hunks": [
{
"added": [
"",
"\tDerby - Class org.apache.derby.ui.popup.actions.AddDerbyNature",
"",
"\tLicensed to the Apache Software Foundation (... |
derby-DERBY-1377-270a34de | DERBY-1377: Rototill tree under java/engine/org/apache/derby/impl/store/
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429802 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/xact/XactXAResourceManager.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" ... |
derby-DERBY-1377-2dd2d112 | DERBY-1377: (Partial) Dag's changes to iapi/sql/execute
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429920 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/execute/TupleFilter.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work f... |
derby-DERBY-1377-2e658c29 | DERBY-1377: (Partial) - Dag's adjustments to iapi/sql/dictionary
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429918 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/dictionary/ViewDescriptor.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this ... |
derby-DERBY-1377-3dc2ce45 | DERBY-1377 (partial): Update the rest of the files in java/tools.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429860 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/tools/sysinfo.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for additional in... |
derby-DERBY-1377-4ecc65a1 | DERBY-1377 (partial): cleanup a couple of missed files, insert proper license
header into the generated ClassSizeCrawler.java
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@430149 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1377-575d6a11 | DERBY-1377: (Partial) Dag's changes to impl/sql/conn for the license header
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429828 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/conn/TempTableInfo.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work fo... |
derby-DERBY-1377-59bf37d1 | DERBY-1377 (partial): Update license headers for client
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429795 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/jdbc/ClientXADataSource40.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for ... |
derby-DERBY-1377-666eb9fe | DERBY-1377: (Partial) - Dag's changes to iapi/sql/depend
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429914 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/depend/ProviderList.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work f... |
derby-DERBY-1377-6baf18bb | DERBY-1377: Rototill tree under java/engine/org/apache/derby/iapi/services/
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429811 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/uuid/UUIDFactory.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work... |
derby-DERBY-1377-6d913c60 | DERBY-1377 (partial): Update license headers in impl/load
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429897 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/SqlXmlExecutor.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this wor... |
derby-DERBY-1377-75588ca7 | DERBY-1377: (Partial) - Dag's mods to iapi/sql/conn
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429867 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/conn/StatementContext.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work... |
derby-DERBY-1377-75c7276a | DERBY-1377: Rototill tree under java/engine/org/apache/derby/iapi/store/
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429816 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/store/raw/xact/TransactionId.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this w... |
derby-DERBY-1377-93fea347 | DERBY-1377: Rototilled tree under java/engine/org/apache/derby/impl/services/
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429794 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/uuid/BasicUUIDGetter.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this ... |
derby-DERBY-1377-9a7cd7e8 | DERBY-1377: (Partial) Updated the tools/sysinfo directory to use the
new license header
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429515 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/impl/tools/sysinfo/ZipInfoProperties.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this... |
derby-DERBY-1377-b3ef6b5b | DERBY-1377: Rototill java/shared/org/apache/derby/shared/common/error/
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429771 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/shared/org/apache/derby/shared/common/error/ExceptionUtil.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this w... |
derby-DERBY-1377-c38b8415 | DERBY-1377: Update license headers in org.apache.derbyTesting.unitTests
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429812 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/unitTests/util/MsgTrace.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this wor... |
derby-DERBY-1377-d4580ab6 | DERBY-1377: (Partial) Dag's updates to iapi/sql/compile
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429863 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/compile/Visitor.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for a... |
derby-DERBY-1377-de243e0f | DERBY-1377: (Partial) - Updated license headers for the build
subtree.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429495 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/build/org/apache/derbyBuild/splitmessages.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
" this work for addition... |
derby-DERBY-1377-dff95a18 | DERBY-1377: Fix license headers on remaining java files.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@430143 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1377-f6123eea | DERBY-1377: (Partial) - Dag's changes to sql/execute
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@429838 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/WriteCursorConstantAction.java",
"hunks": [
{
"added": [
" Licensed to the Apache Software Foundation (ASF) under one or more",
" contributor license agreements. See the NOTICE file distributed with",
"... |
derby-DERBY-1379-e1e03892 | DERBY-1379: Committed Olav's autoload.diff. This fixes the problem which caused all of the nist tests to fail when derbyall was run against jar files under jdk1.6 with the db2jcc jar in the classpath.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@412859 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/harness/RunList.java",
"hunks": [
{
"added": [
"import java.sql.DriverManager;",
"import java.sql.SQLException;",
""
],
"header": "@@ -42,6 +42,9 @@ import java.util.Enumeration;",
... |
derby-DERBY-1380-7c3b39d5 | DERBY-1380: Commit Dyre's derby-1380,v1.diff patch, which makes it possible to connect to Derby databases when running under build 86 of jdk1.6.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@412204 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/FailedProperties40.java",
"hunks": [
{
"added": [
"import java.util.Map;",
"import java.util.HashMap;",
"import java.sql.SQLClientInfoException;",
"import java.sql.ClientInfoStatus;",
" * <c... |
derby-DERBY-1380-8a44c0f3 | DERBY-1380: derby-1380.v2.diff, adding new overloads for createQueryObject().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@412239 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetConnection40.java",
"hunks": [
{
"added": [
"import java.sql.Connection;"
],
"header": "@@ -28,6 +28,7 @@ import org.apache.derby.client.am.SqlException;",
"removed": []
}
]
},
{
"file": "... |
derby-DERBY-1382-5fc38c4d | DERBY-1382 lobs fail silently with result sets of type TYPE_SCROLL_INSENSITIVE in client jdbc driver. Contributed by Fernanda Pizzorno.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@414165 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetCursor.java",
"hunks": [
{
"added": [],
"header": "@@ -128,10 +128,6 @@ public class NetCursor extends org.apache.derby.client.am.Cursor {",
"removed": [
" if (hasLobs_) {",
" extdtaPosi... |
derby-DERBY-1386-c1bc7429 | DERBY-1386: Wrong results with query using LIKE and ESCAPE clause that
includes "%", "\", and "_"
Queries using LIKE/ESCAPE could return wrong results if the first
wildcard character was preceded by an even number of escape
characters. This patch fixes the issue by changing the way
Like.lessThanString() parses the pattern string.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@413123 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/Like.java",
"hunks": [
{
"added": [],
"header": "@@ -852,58 +852,6 @@ public class Like {",
"removed": [
"\t/**",
"\t * Return the substring from the pattern for the < clause.",
"\t * (NOTE: This m... |
derby-DERBY-1387-5b508872 | DERBY-1387 Make the registration of MBeans with JMX robust in the case of permission issues. Stops a hang in derbynet._Suite where a network server was booted with insufficient permissions for MBeans.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@636583 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/jmx/JMXManagementService.java",
"hunks": [
{
"added": [
" // Ignoring inability to create or",
" // find the mbean server. MBeans can continue",
" // to be registered with this ... |
derby-DERBY-1387-5c4e302b | DERBY-1387 Expose an api in ManagementService to register and unregister Mbeans. Use this for a simple JDBCMBean that reports some information about the JDBC driver.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@627877 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/jmx/ManagementService.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.error.StandardException;",
""
],
"header": "@@ -17,6 +17,8 @@",
"removed": []
}
]
},
{
"file": ... |
derby-DERBY-1387-6597e569 | DERBY-1387 (partial) Add a VersionMBean for the network server code.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@629278 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.reference.Module;",
"import org.apache.derby.iapi.services.info.Version;",
"import org.apache.derby.iapi.services.jmx.ManagementSe... |
derby-DERBY-1387-a3ffa1e0 | DERBY-1387, DERBY-3385, DERBY-3435 Add a ManagementMBeanTest which requires some refactoring of the MBeanTest to have the JMX setup moved from VersionMBeanTest. Fix VersionMBean not to have the BuildNumberAsInt attribute and rename MaintananceVersion to match the spec and the tests.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@631372 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/info/Version.java",
"hunks": [
{
"added": [
" public int getMaintenanceVersion(){"
],
"header": "@@ -63,7 +63,7 @@ public class Version implements VersionMBean {",
"removed": [
" public int ... |
derby-DERBY-1387-c970168c | DERBY-1387 (partial) Establish a pattern of registering a Derby mbean using StandardMBean. This allows the MBean interface and implementation class to be in separate packages (and if required have unrelated names). This means the public api org.apache.derby.mbeans is not forced to contain the implementation of the MBeans and thus have references to other classes that are not part of the public api.
Fix the build order for o.a.d.mbeans to be early since it does not depend on internal classes and should not require JDK 1.5.
Added a version string attribute to the VersionMBean that shows the full version.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@627131 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/info/Version.java",
"hunks": [
{
"added": [
" Derby - Class org.apache.derby.iapi.services.info.Version"
],
"header": "@@ -1,6 +1,6 @@",
"removed": [
" Derby - Class org.apache.derby.mbeans.Ve... |
derby-DERBY-1387-e4f7f9e7 | DERBY-1387 Cleanup some details of the ManagementService api based upon feedback from John Embretsen. Mainly rename 'nameAttributes' to 'keyProperties' to match JMX terminology
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@628836 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/jmx/ManagementService.java",
"hunks": [
{
"added": [
" * The mbean will be unregistered automatically when Derby shuts down.",
" * @param keyProperties The String representation of the MBean's key properties,",
... |
derby-DERBY-1387-f8bc0199 | DERBY-3424 (partial) Add initial apis and bean implementations for a management
mbean to control Derby's JMX behaviour. Start and stop the management are
present as operations but currently do nothing. Also fix a bug in DERBY-1387
where shutting down Derby would fail with jmx when multiple mbeans were registered.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@628142 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/jmx/ManagementService.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.reference.Module;",
"import org.apache.derby.mbeans.ManagementMBean;"
],
"header": "@@ -18,6 +18,8 @@",
"removed"... |
derby-DERBY-1392-0a625f3a | DERBY-1392, committed patch submitted by Anders Morken
RAFContainer.java#writePage(...) will
attempt to retry a write if an IOException is thrown on the first attempt.
However, the next attempt does not add container header data to the first page, nor does it encrypt the data if the database is encrypted as the wrong buffer
is used in the catch block.
I'd expect this bug to be case silent corruption of encrypted databases if the
code path was actually exercised. The fact that this bug still lives and
nobody has discovered it is possibly an indication of how uncommon this code
path is. Since the comment in the code says nothing about exactly what
platforms the workaround was intended for, I don't know if these platforms are
still supported for Derby.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@414647 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/RAFContainer.java",
"hunks": [
{
"added": [
" {",
" // committed and dropped, do nothing.",
" // This file container may only be a stub",
"",
"... |
derby-DERBY-1393-054fa3a5 | DERBY-1393: PreparedStatement.setObject(int,Object,int) should throw
SQLFeatureNotSupportedException for unsupported types
Description of the patch:
The new setObject() methods call checkForSupportedDataType() to
check whether targetSqlType is supported.
Added a new error message "The data type ''{0}'' is not supported."
with SQL state 0A000 (which ensures that the exception is converted
to SQLFeatureNotSupportedException). This error message is used when
targetSqlType is not supported.
Added more JDBC 4.0 constants (from java.sql.Types) to
JDBC40Translation and created a test JDBC40TranslationTest which
tests that the constants are correct (the values of the constants
are hard coded, so we don't get the compile-time check as with
JDBC{2,3}0Translation).
New test case SetObjectUnsupportedTest which is run as part of
PreparedStatementTest and CallableStatementTest in the jdbc40 suite.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@420436 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/PreparedStatement.java",
"hunks": [
{
"added": [
"import org.apache.derby.shared.common.reference.JDBC40Translation;"
],
"header": "@@ -20,6 +20,7 @@",
"removed": []
},
{
"added": [
... |
derby-DERBY-1396-00b4912a | - DERBY-1396 ReEncodedInputStream may fail to read all of source Reader - Patch by Tomohito Nakayama (tomonaka@basil.ocn.ne.jp)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@413901 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/ReEncodedInputStream.java",
"hunks": [
{
"added": [
"\t\tint count;",
"\t\tdo{",
"\t\t\tcount = reader.read(decodedBuffer_, 0, BUFFERED_CHAR_LEN);",
"\t\t\t",
"\t\t}while(count == 0);",
... |
derby-DERBY-1417-16e10039 | DERBY-1417 (partial) Add new, lengthless overloads to the streaming api
Disable five test cases in the DerbyNetClient framework. Patch
contributed by Kristian Waagan.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@423068 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1417-57154353 | DERBY-1417: Add new, lengthless overloads to the streaming api
'derby-1417-1a-notImplemented.diff' adds a number of new lengthless
streaming overloads that Derby will not support. All methods added by the
patch throw not-implemented exceptions. We don't support them because we
either don't support the data type or because we don't yet support named
parameters in CallableStatement.
Patch submitted by Kristian Waagan.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@417753 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ResultSet.java",
"hunks": [
{
"added": [
" public void updateNCharacterStream(int columnIndex, Reader x)",
" throws SQLException {",
" throw jdbc3MethodNotSupported();",
" }",
... |
derby-DERBY-1417-c586481b | DERBY-1417 (partial) Add new, lengthless overloads to the streaming api
Add the new overloads to the Brokered* classes and update
UnsupportedVetter with the methods we support.
Patch contributed by Kristian Waagan.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@423807 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/jdbc/BrokeredCallableStatement40.java",
"hunks": [
{
"added": [
"",
" public final void setNCharacterStream(String parameterName, Reader value)",
" throws SQLException {",
" getCallableSta... |
derby-DERBY-1417-ef4a7ba6 | DERBY-1417: Commit derby-1417-7a-clientborderfix.diff, fixing a hang on a border condition.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@427969 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/ByteArrayCombinerStream.java",
"hunks": [
{
"added": [
" *",
" * If there is less data available than the specified length, an exception is",
" * thrown. Available data is determined by the length of the byte array... |
derby-DERBY-1421-cfcbbae5 | DERBY-1421 updates of LOBs fails with scrollable updatable result sets. Contributed by Fernanda Pizzorno
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@418221 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1434-34a7cbef | DERBY-1434: Client can send incorrect database name to server after
having made multiple connections to different databases.
Patch contributed by Julius Stroffek.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@478877 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/DRDAConnThread.java",
"hunks": [
{
"added": [
" ",
" // A check that the rdbnam field corresponds to a database",
" // specified in a ACCRDB term.",
" ... |
derby-DERBY-1439-a11b0768 | DERBY-1439: Remove the AntiGC thread
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1027552 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/services/monitor/BaseMonitor.java",
"hunks": [
{
"added": [],
"header": "@@ -88,9 +88,6 @@ import java.util.NoSuchElementException;",
"removed": [
"import java.security.AccessController;",
"import java.security.Pr... |
derby-DERBY-1440-2b22c7f1 | DERBY-1440: jdk 1.6 client driver omits SQLStates and chained
exceptions in error messages
Follow-up patch which simplifies wrapInSQLException() and improves the
comments.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@542232 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/TransactionResourceImpl.java",
"hunks": [
{
"added": [
" * </PRE>"
],
"header": "@@ -101,6 +101,7 @@ import java.sql.SQLException;",
"removed": []
},
{
"added": [
"\t/**"
]... |
derby-DERBY-1440-de3b1087 | DERBY-1440: jdk 1.6 client driver omits SQLStates and chained exceptions in
error messages
While working on DERBY-2472 I found out what caused this difference between
the JDBC 3.0 driver and the JDBC 4.0 driver. There are three
problems. Firstly, StandardException.unexpectedUserException() doesn't
recognize that an SQLException is generated Derby since it is not an
EmbedSQLException. Secondly, TransactionResourceImpl.wrapInSQLException()
invokes SQLException.setNextException() explicitly so that the required
chaining/ferrying logic in the exception factory and in EmbedSQLException's
constructor is not used. Thirdly,
SQLException40.wrapArgsForTransportAcrossDRDA() puts a standard
SQLException, not an EmbedSQLException, in the argument ferry's
next-exception chain, which prevents the network server from seeing it as a
Derby exception.
The attached patch fixes the problem by
1) using SQLExceptionFactory.getArgumentFerry() to find out whether the
exception is a Derby exception in unexpectedUserException()
2) using factory methods instead of setNextException() to do the chaining
in wrapInSQLException()
3) improving Util.javaException() so that it sets up a next-exception
chain if the Java exception contains nested exceptions
4) changing wrapArgsForTransportAcrossDRDA() to create an argument ferry
whose next exception is the argument ferry of the main exception's next
exception
This patch also fixes all the JUnit tests that contain code looking like this:
assertStatementError(JDBC.vmSupportsJDBC4() ? "38000" : "42X62", cSt);
Now, the check for JDBC level is not needed anymore for those tests.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@541435 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/error/StandardException.java",
"hunks": [
{
"added": [
"import org.apache.derby.impl.jdbc.Util;"
],
"header": "@@ -24,6 +24,7 @@ package org.apache.derby.iapi.error;",
"removed": []
},
{
"added":... |
derby-DERBY-1443-6796671f | DERBY-1443: DataTypeDescriptor.isBinaryType() return false for Types.BLOB
Adding javadoc for isBinaryType() and isCharacterType() clarifying why
they return false for BLOB and CLOB.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@423827 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/types/DataTypeDescriptor.java",
"hunks": [
{
"added": [
"\t/**",
"\t * Check whether a JDBC type is one of the character types that are",
"\t * compatible with the Java type <code>String</code>.",
"\t *",
... |
derby-DERBY-1445-c5114100 | DERBY-1445: Add new streaming overloads and modify some existing ones.
Adding new (JDBC 4.0) streaming overloads to ResultSet, PreparedStatement
and CallableStatement. The new overloads take a long as the length
parameter.
Patch contributed by V. Narayanan.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@417548 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/PreparedStatement.java",
"hunks": [
{
"added": [
" /**",
" * sets the parameter to the Binary Stream object",
" *",
" * @param parameterIndex the first parameter is 1, the second is 2, ...... |
derby-DERBY-1445-ff7369c4 | DERBY-1445: Add new streaming overloads and modify some existing ones.
Fix test issues. Patch submitted by V. Narayanan.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@417705 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1458-121b2ed0 | DERBY-1458; implement a message check from the build;
third attempt - rewritten as an ant-taskdef (not junit).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@705945 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1459-e3e3ca37 | DERBY-1459: Commit bug1459_v04.diff. This introduces a dummy jdbc driver so that JDBC4 driver autoloading will play well with the engine booting which happens when the public embedded driver classloads.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@421717 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/jdbc/EmbeddedDriver.java",
"hunks": [
{
"added": [
"public class EmbeddedDriver implements Driver {",
"\tprivate\tAutoloadedDriver\t_autoloadedDriver;",
"\t"
],
"header": "@@ -83,13 +83,15 @@ import org.apac... |
derby-DERBY-1464-fee55d87 | DERBY-578 - Grouped select from temporary table raises null pointer exception in byte code generator
DERBY-1464 - runtimestatistics can show that an index is being used even when it isn't
Contributed by Manish Khettry
The problem is simple enough-- we didn't have a conglomerate name for temporary tables. I fixed the code to behave more like what fillInScanArgs does.
Earlier, we would set the indexName field in DistinctScanResult to the conglomerate name (cd.getName()) used to scan the table. If the conglomerate was the base table itself then this was just plain wrong. The change, for this patch, passes null if no index is being used.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@418672 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/FromBaseTable.java",
"hunks": [
{
"added": [
"\t",
" /* helper method used by generateMaxSpecialResultSet and",
" * generateDistinctScan to return the name of the index if the ",
" ... |
derby-DERBY-1465-056e43e9 | DERBY-1465 NetworkServerControl.start() should throw an exception and not just print exceptions if the server fails to start
Backout change until changes from review comments from Dan can be incorporated.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@540809 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [],
"header": "@@ -161,7 +161,6 @@ public final class NetworkServerControlImpl {",
"removed": [
"\t"
]
},
{
"added": [],
"header":... |
derby-DERBY-1465-36cea34a | DERBY-1465; throw an exception in addition to printing one to the log if
NetworkServerControl.start() does not succeed.
Committing patch .diff8
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@729933 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [],
"header": "@@ -62,7 +62,6 @@ import java.util.Vector;",
"removed": [
"import org.apache.derby.iapi.jdbc.DRDAServerStarter;"
]
},
{
"ad... |
derby-DERBY-1465-928226b9 | DERBY-1465; backing out changes after seeing a hang in replicationTests
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@730187 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.jdbc.DRDAServerStarter;"
],
"header": "@@ -62,6 +62,7 @@ import java.util.Vector;",
"removed": []
},
{
"ad... |
derby-DERBY-1465-b700deb3 | DERBY-1465 NetworkServerControl.start() should throw an exception and not just print exceptions if the server fails to start
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@540789 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"\t",
"\t/** Any exception that occurs during ",
"\t * start up will be saved in this variable and",
"\t * thrown by the start method.",
"... |
derby-DERBY-1465-c38c5e1d | DERBY-1465; backing out changes of revision 718616; they cause an intermittent
hang.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@722639 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [],
"header": "@@ -232,7 +232,6 @@ public final class NetworkServerControlImpl {",
"removed": [
"\tprivate Exception runtimeException=null;"
]
},
... |
derby-DERBY-1465-db233518 | DERBY-1465; NetworkServerControl.start() should throw an exception - not just
print an exception - if the server fails to start
Patch initially contributed by Kathey Marsden.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@718616 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java",
"hunks": [
{
"added": [
"\tprivate Exception runtimeException=null;"
],
"header": "@@ -232,6 +232,7 @@ public final class NetworkServerControlImpl {",
"removed": []
},
... |
derby-DERBY-147-be7f461b | DERBY-147: ERROR 42x79 if specify same column twice and use ORDER BY
This patch contributed by Bernd Ruehlicke (apache@priwall.org)
This patch changes the getOrderByColumn method in ResultColumnList so that
it uses ResultColumn.isEquivalent to determine whether the column specified
in the ORDER BY clause is ambiguous or not. It is ok to select the ORDER BY
column multiple times, so long as all the occurrences are equivalent. If there
is an ambiguity, the statement is rejected and the user must reword it to
clarify which column is to be used for ordering the results.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@447877 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/compile/ResultColumnList.java",
"hunks": [
{
"added": [
" /*",
" * A comment on 'orderBySelect'. When we encounter a SELECT .. ORDER BY",
" * statement, the columns (or expressions) in the ORDER BY clause... |
derby-DERBY-1476-dbbf9ff1 | DERBY-1476: PreparedStatement.setNull(int,int) should throw
SQLFeatureNotSupportedException for unsupported types
derby-1476-v1.diff adds a call to checkForSupportedDataType() in
setNull(). It also moves that call in setObject() after 'if (obj ==
null) { setNull(pos, type); return; }' in order to avoid double
checking. New test cases have been added to SetObjectUnsupportedTest
so that it tests setObject(int,Object,int),
setObject(int,Object,int,int), setNull(int,int) and
setNull(int,int,String).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@421255 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/PreparedStatement.java",
"hunks": [
{
"added": [
" checkForSupportedDataType(jdbcType);"
],
"header": "@@ -408,6 +408,7 @@ public class PreparedStatement extends Statement",
"removed": []
},
... |
derby-DERBY-1478-7752cf6d | This patch is for DERBY-2524 (DataTypeDescriptor(DTD) needs to have collation type and collation derivation. These new fields will apply
only for character string types. Other types should ignore them.) and it does following 2 things
1)Add collation type and collation derivation attributes and apis to TypeDescriptor interface and it's implementations.
2)Save the collation type in the scale field of character types in writeExternal method of TypeDescriptorImpl. And read the scale field into
the collation type for character types in readExternal method of TypeDescriptorImpl.
svn stat -q
M java\engine\org\apache\derby\iapi\types\DataTypeDescriptor.java
M java\engine\org\apache\derby\catalog\TypeDescriptor.java
M java\engine\org\apache\derby\catalog\types\TypeDescriptorImpl.java
Details of the patch
1)Added getters and setters for collationType and collationDerivation in TypeDescriptor. In addition, TypeDescriptor has new constants
defined in them which will be used by the rest of the collation related code in Derby. One of the constants is COLLATION_DERIVATION_INCORRECT
I am initializing the collation derivation for all the data types to COLLATION_DERIVATION_INCORRECT in TypeDescriptorImpl. This should get
changed to "implicit" or "none" for character string types before the runtime code kicks in. For all the other types, it will remain set to
COLLATION_DERIVATION_INCORRECT because collation does not apply to those data types.
2)DTD implements the new apis in the TypeDescriptor interface.
3)2 set of changes went into
a)TypeDescriptorImpl has 2 new fields, namely, collationType and collationDerivation. collationDerivation is initialized to
TypeDescriptor.COLLATION_DERIVATION_INCORRECT. For character string types, these field should get set correctly. In addition, there are apis
to set and get values out of these 2 fields.
b)The next change for this class is in writeExternal and readExternal methods. I would like community's feedback on my assumption for this
particular change. The collation type of a character string type will get saved in the existing scale field since scale does not apply to
character string types. My question is about collation derivation. The collation derivation infromation does not get saved like collation
type. But may be that is ok because I am assuming that writeExternal and readExternal get called only for the persistent columns (ie columns
belonging to system and user tables). Collation derivation of such character string columns (coming from persistent tables) is always
implicit. And, hence in readExternal, for character string types, I can initialize collation derivation to be implicit. My assumption is
that readExternal and writeExternal methods will never get called for character string types with collation of none or explicit. Today we
don't have explicit as one of the possible values for collation derivation, but a character string type will have the collation derivation
of none if it was the result of an aggregate method involving operands with different collation derivations. This comes from item 11) from
Section Collation Determination section at http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478
Questions
1)I have included all the constant definitions related to collation in TypeDescriptor. If anyone has suggestion on a better place to
define them, let me know. Wonder if there is already a class to define miscellaneous constant definitions like the ones I have added.
TypeDescriptor does look like a good place for these constants defined by me because these constants all belong to the data type world.
2)Is it right to assume that readExternal and writeExternal methods in TypeDescriptorImpl will get called only for persistent columns?
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@525568 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/TypeDescriptor.java",
"hunks": [
{
"added": [
"\t/**",
"\t For a character string type, the collation derivation should always be ",
"\t \"explicit\"(not possible in Derby 10.3), \"implicit\" or \"none\". We will "... |
derby-DERBY-1478-869152fa | DERBY-2335
Made changes such that rather than having a new method in BaseTypeCompiler to push the DVD on the stack at code generation time, we use the
existing method that accomplishes the same task in ExpressionClassBuilder. The junit tests have run fine with these changes and the stack
trace experienced by Army in DERBY-2335 has been fixed by this fix. The reason for stack trace was that the lifetime of a BaseTypeCompiler
is longer than a single class generation and I was trying to hold a reference to a declared method from MethodBuilder.describeMethod across
the generated classes. This discussion can be found at
http://www.nabble.com/DERBY-1478-subtask-DERBY-2583---need-help-in-debugging-stack-trace-thrown-during-code-generation-p10611184.html
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@538325 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/compile/TypeCompiler.java",
"hunks": [
{
"added": [
"import org.apache.derby.impl.sql.compile.ExpressionClassBuilder;"
],
"header": "@@ -25,6 +25,7 @@ import org.apache.derby.iapi.services.loader.ClassFactory;",
... |
derby-DERBY-1478-96a630c7 | Submitting a patch (DERBY2524_Collation_Info_In_DTD_v2_diff.txt) attached to DERBY-2524. This is a followup to the earlier commited patch (DERBY2524_Collation_Info_In_DTD_v1_diff.txt svn revision 525568)
svn stat -q
M java\engine\org\apache\derby\iapi\types\DataTypeDescriptor.java
M java\engine\org\apache\derby\iapi\types\StringDataValue.java
M java\engine\org\apache\derby\catalog\TypeDescriptor.java
M java\engine\org\apache\derby\catalog\types\TypeDescriptorImpl.java
The patch does following to address feedback received on the earlier patch in thread http://www.nabble.com/-jira--Created%3A-%28DERBY-2524%29-DataTypeDescriptor%28DTD%29-needs-to-have-collation-type-and-collation-derivation.-These-new-fields-will-apply-only-for-character-string-types.-Other-types-should-ignore-them.-p9842379.html
1)Moved the constant definitions from TypeDescriptor to StringDataValue.
2)Added javadoc comments for all the constants. One big javadoc comment for one of the constants in the related constants and other
constants in that group will just have a javadoc of @see.
3)I had used string costants for collation derivation since they are more verbose. But that is more expensive than simply using
int. As a middle ground, I have defined collation derivation constants as int but the names of the constants are verbose :)
I also changed the api for collation derivation to work with int rather than String. Finally, changed collationDerivation from
String to int in TypeDescriptorImpl.
4)Rather than using "error" to indicate incorrect collation derivation, we will just initialize collation derivation to "none".
For all character string types, the collation derivation should get changed to "implicit" unless we are working with aggregate
result type of character string type and the operands to the aggregate have different collation types.
5)Currently, I only save collation type of a persistent character string type column into SYSCOLUMNS's COLUMNDATATYPE column. Collation
derivation for such character string type is assumed as "implicit" because that is the only possible option in Derby 10.3 for persistent
columns. But in some future release of Derby, when we will start supporting SQL COLLATE clause, we will want to differentiate between
"explicit" and "implicit" collation derivation for such persistent columns. So, may be it will be good for us to start saving collation
derivation too. For now, I have added this task as a line item under wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478 under "Performance/Desirable items" section.
6)I caused several javadoc errors for using @see Classname.methodname rather than @see Classname#methodname. Sorry about that. Fixed
those errors in this patch.
I think with this patch, I have taken care of all the feedback received on the earlier patch DERBY2524_Collation_Info_In_DTD_v1_diff.txt.
Again, if anyone has any comment on this committed patch or earlier commit svn revision 525568, please send your feedback on
Derby mailing list.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@525729 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/catalog/TypeDescriptor.java",
"hunks": [
{
"added": [],
"header": "@@ -46,31 +46,6 @@ public interface TypeDescriptor",
"removed": [
"\t/**",
"\t For a character string type, the collation derivation should always be ... |
derby-DERBY-1481-1b7b14f6 | DERBY-1481: Client driver: ResultSet.beforeFirst() gives protocol
error on scrollable, updatable result sets that are downgraded to
read-only
When the result set is downgraded from updatable to read-only because
the query generating the result set cannot produce an updatable result
set, the result set will be downgraded on the server side, and a
warning (SQLCARD) indicating the downgrade will be sent to the
client. Warnings on the server side are not cleared after they are
sent to the client causing the server to send the same warning several
times.
Positioning commands like ResultSet.beforeFirst() that do not return
any data also do not expect warnings to be returned. The protocol
error was being caused by this downgrade warning that was being sent
several times, one of them being in a response to a
ResultSet.beforeFirst() command.
The attached patch (derby-1481.diff) fixed the problem by clearing the
warnings after they are sent so that the same warning will not be sent
more than once.
The patch was contributed by Fernanda Pizzorno.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@421887 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-0be8cb53 | DERBY-1482
This commit adds a new test case which creates a table with LOB column and insets large data into that column. There is a trigger defined on this table but the trigger does not need access to the LOB column. In 10.8 and prior releases, even though we don't need the LOB column to execute the trigger, we still read all the columns from the trigger table when the trigger fired. With 10.9, only the columns required by the firing triggers are read from the trigger table and hence for our test here, LOB column will not be materialized. In 10.8 and prior releases, the trigger defined in this test can run into OOM errors depending on how much heap is available to the upgrade test and hence the test will make sure that we do not fire the trigger is 10.8 and lower. But in 10.9 and higher, OOM won't happen for this test because LOB is never read into memory because it is not needed for the firing trigger.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1134467 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-168be4e5 | DERBY-1482 / DERBY-5121
Rick Hillegas contributed a very exhaustive trigger test which I am converting to junit and adding to the upgrade suite
// The test exhaustively walks through all subsets and permutations
// of columns for a trigger which inserts into a side table based on
// updates to a master table.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1125453 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-3b2562cf | DERBY-1482: Fixed JavaDoc warnings (introduced in r915177).
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@915310 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-56bebbea | DERBY-5121 Data corruption when executing an UPDATE trigger
With the earlier checkin for DERBY-5121, DERBY-1482 changes weren't completely backed out on trunk and 10.7. We have backed out
the code for the triggers so that now triggers look for the columns in their actual column positions at execution time. But
DERBY-1482 also made changes to UPDATE code to read only the colunms needed by it and the triggers that it is going to fire.
We need to backout the changes to UPDATE code to make sure that it reads all the columns from the trigger table and not do
selective column reading.
Also adding an upgrade case testing the behavior of UPDATE reading correct columns from the trigger table so that trigger
finds the columns it needs.
derbyall and junit suite runs fine with these changes
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1087049 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-6f271b4b | DERBY-1482/DERBY-5121
Rick Hillegas contributed a trigger test for DERBY-1482/DERBY-5121. With revision 1125453, that test was added to Changes10_8 but this test really is applicable for upgrades from all releases and should not be added into a specific version upgrade test. As a result, I am moving the test from Changes10_8.java to BasicSetup.java. This will ensure that the trigger test will get run for upgrades from all previous releases.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1130895 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-c1193bf7 | DERBY-5121 Data corruption when executing an UPDATE trigger
Committing changes to back out DERBY-1482 out of trunk(10.8 codeline). The changes have already been backed out of 10.7). In addition to engine code backport, it will also disable the tests that were added for DERBY-1482.
With DERBY-1482, these tests would not read in large object columns into memory because the triggers didn't need them. But now that DERBY-1482 changes are being backed out, the large object columns will be read in which can cause the test to run out of memory depending on how much heap is available to it. I will disable the tests from 10.7 too.
This commit also has a comment in DataDictionaryImpl:getTriggerActionString explaining the code changes for backout. I will add that comment in 10.7 too.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1084718 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
"\t\t// DERBY-1482 has caused a regression which is being worked",
"\t\t// under DERBY-5121. Until DERBY-5121 is fixed, we want",
"\t\t// Derby to create tri... |
derby-DERBY-1482-c4728eba | DERBY-1482 (Update triggers on tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed.)
Reduced the size of LOBs in the test to 50MB since junit-lowmem gets run with 16MB and hence no need to read unnecessarily larger LOB(the test was testing with 300MB lobs).
Also, some subset of tests are relying on DriverManager which is not available with J2ME. I have disabled those subset of tests to not run under J2ME framework.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@957785 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1482-d9d1bc8e | DERBY-1482 Update triggers on tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed.
This commit ensures that we read only the necessary columns during triggering sql's execution rather than read all the columns
from the trigger table just be cause there is a trigger defined on the table. The triggering sql might need more columns
in it's resultset than what a firing trigger might need during it's execution. So, in addition to reading only the columns
reuired by the triggering sql(which also includes all the columns required by it's triggers which will get fired), the
other thing commit does is to carve out a temporary resulset for every firing trigger with just the columns that the
trigger needs. This temporary resultset can be exactly same as the resulset created by the triggering sql or a subset of
the resulset created by the triggering sql, it all depends on what columns the firing trigger needs during it's
execution. Once the right resulset set is constructed for the firing trigger, the trigger will be able to find the columns
referenced in it's trigger action through the REFERENCING clause in the correct positions in the resulset.
With this commit, when the trigger action SPSes needs to be regenerated(or for a new trigger, when it is getting generated the
first time). the generated trigger action SPSes will look for the columns getting used through the REFERENCING
clause through their relative position in the temporary resultset which will be generated for each of the firing triggers.
In the prior releases, since we were reading all the columns from the triggering table, the columns were looked in their
actual physical position in the trigger table.
The commit also ensures that all the above mentioned code changes to be selective about columns getting read from the trigger
table should only happen with a database marked as 10.9 release. In prior release databases(in other words, we are in
soft-upgrade mode), we do not want to be selective about what columns get read because when soft-upgrade database is taken
back to it's original release, that release will not be able to work correctly since it doesn't recognize the column
read optimization.
The commit also enables the trigger test cases which test that unnecessary LOB columns are not getting read during trigger
execution when they are not really needed by the triggering sql and the firing triggers.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1103992 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java",
"hunks": [
{
"added": [
"\t\t// If we are dealing with database created in 10.8 and prior,",
"\t\t// then we must be in soft upgrade mode. For such databases,",
"\t\t// we want to g... |
derby-DERBY-1482-df731e99 | DERBY-5121 Data corruption when executing an UPDATE trigger
Changes made for DERBY-1482 caused corruption which is being worked
under DERBY-5121. The issue is that the generated trigger action
sql could be looking for columns (by positions, not names) in
incorrect positions. With DERBY-1482, trigger assumed that the
runtime resultset that they will get will only have trigger columns
and trigger action columns used through the REFERENCING column.
That is an incorrect assumption because the resultset could have
more columns if the triggering sql requires more columns. DERBY-1482
changes are in 10.7 and higher codelines. Because of this bug, the
changes for DERBY-1482 have been backed out from 10.7 and 10.8
codelines so they now match 10.6 and earlier releases. This in
other words means that the resultset presented to the trigger
will have all the columns from the trigger table and the trigger
action generated sql should look for the columns in the trigger
table by their absolution column position in the trigger table.
This disabling of code will make sure that all the future triggers
get created correctly. The existing triggers at the time of
upgrade (to the releases with DERBY-1482 backout changes in them)
will get marked invalid and when they fire next time around with
the release with DERBY-1482 changes backed out, the regenerated sql
for them will be generated again and they will start behaving
correctly. So, it is *highly* recommended that the users upgrade
from 10.7.1.1 to next point release of 10.7 or to 10.8
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1085613 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1484-14cec7cc | DERBY-1484: Client and embedded behave differently when the table name is null in DatabaseMetaData methods.
Patch file: DERBY-1484-4_ExcFact.diff
Patch contributed by Jørgen Løland.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@537882 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/EmbedDatabaseMetaData.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.reference.SQLState;"
],
"header": "@@ -37,6 +37,7 @@ import org.apache.derby.iapi.error.StandardException;",
"removed": []
... |
derby-DERBY-1489-ee5857f3 | DERBY-1489: Provide ALTER TABLE DROP COLUMN functionality
This patch provides support for ALTER TABLE t DROP COLUMN c.
The patch modifies the SQL parser so that it supports statements of the form:
ALTER TABLE t DROP [COLUMN] c [CASCADE|RESTRICT]
If you don't specify CASCADE or RESTRICT, the default is CASCADE.
If you specify RESTRICT, then the column drop will be rejected if it would
cause a dependent view, trigger, check constraint, unique constraint,
foreign key constraint, or primary key constraint to become invalid.
Currently, column privileges are not properly adjusted when dropping a
column. This is bug DERBY-1909, and for now we simply reject DROP COLUMN
if it is specified when sqlAuthorization is true. When DERBY-1909 is fixed,
the tests in altertableDropColumn.sql should be merged into altertable.sql,
and altertableDropColumn.sql (and .out) should be removed.
This new feature is currently undocumented. DERBY-1926 tracks the documentation
changes necessary to document this feature.
The execution logic for ALTER TABLE DROP COLUMN is in AlterTableConstantAction,
and was not substantially modified by this change. The primary changes to
that existing code were:
- to hook RESTRICT processing up to the dependency manager so that
dependent view processing was sensitive to whether the user
had specified CASCADE or RESTRICT
- to reread the table descriptor from the catalogs after dropping all the
dependent schema objects and before compressing the table, so that the
proper scheman information was used during the compress.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@453420 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/dictionary/SPSDescriptor.java",
"hunks": [
{
"added": [
"\t\t\tcase DependencyManager.DROP_COLUMN_RESTRICT:"
],
"header": "@@ -908,6 +908,7 @@ public class SPSDescriptor extends TupleDescriptor",
"removed": []
... |
derby-DERBY-149-cd24ce30 | DERBY-149
Fix Server hang when invalid string is bound to datetime columns.
Changes network server to skip only the current DSS and not all chained DSS's
when parsing parameter data in SQLDTA.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@291721 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/util/TestUtil.java",
"hunks": [
{
"added": [
"\t public static String getNameFromJdbcType(int jdbcType) {"
],
"header": "@@ -439,7 +439,7 @@ public class TestUtil {",
"removed": [
"\t pu... |
derby-DERBY-1496-1146ea1a | DERBY-1496 - speeding up NSSecurityMechanismTest by shutting down database before bouncing server, so sleeping is not necessary. Also made methods private where possible.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@533889 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1496-1b46090f | DERBY-1496: committing patch DERBY-1496_20070321.diff.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@521055 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/junit/JDBCDataSource.java",
"hunks": [
{
"added": [
" // commenting out until such time as setShutdownDatabase is",
" // supported by client",
" //setBeanProperty(ds, \"shutdownDatabase\", \"shut... |
derby-DERBY-1496-c774a1c4 | DERBY-1496 - (initial checkin)
Add tests that will replace the various *users* tests, as well as dataSourcePermissions* and testSecMec.java.
Some test cases were moved from dataSourcePermissions(_net) to checkDataSource.java.
The *AuthenticationTests can not yet be run successfully, because the junit framework's tearDown() attempts to call ds.shutdownDatabase which is not available with ClientDataSources.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@517483 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1500-27190db9 | DERBY-1500: PreparedStatement#setObject(int parameterIndex, Object x)
throws SQL Exception when binding Short value in embedded mode
setObject(int, Byte) is translated to setByte(int, byte)
setObject(int, Short) is translated to setShort(int, short)
Added test cases in jdbcapi/parameterMapping.java.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@434309 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/EmbedPreparedStatement.java",
"hunks": [
{
"added": [
"\t\t// Byte and Short were added to the table in JDBC 4.0."
],
"header": "@@ -1201,6 +1201,7 @@ public abstract class EmbedPreparedStatement",
"removed": [... |
derby-DERBY-1503-4f9187ed | DERBY-1503: Make jdbc4/StatementEventsTest.junit test callable statements
The patch changes StatementEventsTest the following way:
1) New methods setXA() and setCallable() which make it possible to
use the same test method to test XAConnection/PooledConnection
and PreparedStatement/CallableStatement.
2) Split the test methods into smaller ones.
3) Use asserts to report errors instead of System.out.println().
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@421218 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-151-078bb792 | DERBY-151 Thread termination -> XSDG after operation is 'complete'
This patch catches the exception seen by RAFContainer4
readFull/Write/full when the embedding application thread sees an
interrupt, and asks the user to inspect the app to find the cause.
Before this patch, the symptoms were puzzling to the user, suggesting
that the disk might be full.
The database level error seen is XSDG9:
"Derby thread received an interrupt during a disk I/O operation, please check your application for the source of the interrupt. "
A new store test, Derby151Test, checks this behavior.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@886831 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/data/FileContainer.java",
"hunks": [
{
"added": [
"\t * @exception StandardException Derby Standard error policy",
" throws IOException, StandardException"
],
"header": "@@ -903,9 +903,10 @@ ... |
derby-DERBY-151-59ff24ce | DERBY-151 Thread termination -> XSDG after operation is 'complete'
Follow-up patch derby-151-followup; improves the test to also use client/server.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@886963 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-1511-ec6fcf1f | DERBY-1511: SELECT clause without a WHERE, causes an Exception when
extracting a Blob from a database
Disable bulk fetching for table scans that fetch BLOB or CLOB columns,
if the cursor is holdable, as the large objects in the internal buffer
will not survive across transaction boundaries.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@997722 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/sql/execute/ResultSetFactory.java",
"hunks": [
{
"added": [
" @param disableForHoldable Whether or not bulk fetch should be disabled",
" at runtime if the cursor is holdable."
],
... |
derby-DERBY-1516-f433a645 | DERBY-1516: Inconsistent behavior for getBytes and getSubString for
embedded versus network. Contributed by Craig Russell
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@430825 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Blob.java",
"hunks": [
{
"added": [
" /**",
" * Returns as an array of bytes part or all of the <code>BLOB</code>",
" * value that this <code>Blob</code> object designates. The byte",
" * array co... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.