id stringlengths 22 25 | commit_message stringlengths 137 6.96k | diffs listlengths 0 63 |
|---|---|---|
derby-DERBY-949-e72bcdd3 | DERBY-949: Clean up tests to use common method to get connection.
Committed for Myrna Van Lunteren <m.v.lunteren@gmail.com>
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@386216 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/util/TestUtil.java",
"hunks": [
{
"added": [
" public static Connection getConnection(String databaseName, String connAttrs)",
" \tthrows SQLException {",
" try {",
" C... |
derby-DERBY-953-64e17680 | DERBY-953: Add Statement.isClosed() JDBC4 method
DERBY-1097: Add tests for Statement.isClosed() JDBC4 method
Contributed by Kristian Waagan.
I modified his patch for DERBY-953 to match
Dan's suggested approach. I also added StatementTest.junit to the jdbc40
test suite, which passes. Since this is a JDBC40-specific feature, and
only new code has been added (no existing code has been modified) I did
not run derbyall
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@388234 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-953-a1a7f8ba | DERBY-953 (partial) Add/expand javadoc comments for EmbedStatement.checkStatus and checkExecStatus.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@388227 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/jdbc/EmbedStatement.java",
"hunks": [
{
"added": [
"\t/**",
" * Throw an exception if this Statement has been closed explictly",
" * or it has noticed it has been closed implicitly.",
" * JDBC spec... |
derby-DERBY-96-37551192 | committing tests for DERBY-96 for suresh.thalamati@gmail.com
Attached are some functional tests to test the transaction log checksum feature (Derby-96).
Log corruption is simulated using a proxy storage factory that allows corruption of
the log write request before being writing to the disk. CorruptDiskStorage factory by default forwards
all the request to the underlying disk storage factory except when corruption flags are enabled.
Recovery tests need to boot the same database many times and have to use the
different Subprotocol to enable the corruption instead of the default protocol. This seems to be
possible only by adding a new tests suite in the current test frame work. Added a new suite
called "storerecovery" , may be all future recovery tests can be added to this suite.
git-svn-id: https://svn.apache.org/repos/asf/incubator/derby/code/trunk@169737 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/util/corruptio/CorruptibleIo.java",
"hunks": [
{
"added": [
"/*",
"",
" Derby - Derby - Class org.apache.derbyTesting.functionTests.util.corruptio.CorruptibleIo",
"",
" Copyrigh... |
derby-DERBY-96-c2afcc17 | committing upgrade change related to DERBY-96 for suresh.thalamati.suresh.thalamati@gmail.com
Attached is the new patch with the suggested changes to make
softupgrade correctly with the transaction log
checksum feature in 10.1 Added checkVersion() method to log factory it
self, becuase that is where
the version numbers are read from from the log control file , but did
not export the call it to the
rawstore factory as it is not needed now. (This can be done easlily
when there is a need for upgrade
checks in the other store modules..)
git-svn-id: https://svn.apache.org/repos/asf/incubator/derby/code/trunk@164994 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/store/raw/log/LogAccessFile.java",
"hunks": [
{
"added": [
"import org.apache.derby.iapi.store.raw.RawStoreFactory;"
],
"header": "@@ -35,6 +35,7 @@ import java.util.LinkedList;",
"removed": []
},
{
... |
derby-DERBY-961-c4229c97 | DERBY-961: Error 22001 can include 'XX-RESOLVE-XX' which should be removed
In some cases, error 22001 can come up as follows:
A truncation error was encountered trying to shrink
CHAR () FOR BIT DATA 'XX-RESOLVE-XX' to length 40.
This message makes it appear as if there is a column called XX-RESOLVE-XX,
however, this string is hard-coded in SQLBinary.java, and should be removed.
The intent of the XX-RESOLVE-XX message parameter is to hold the actual
value which could not be shrunk to fit in the column. For a SQLBinary
data type, the actual value may not be human-readable, and so cannot
be displayed.
This patch changes the XX-RESOLVE-XX parameter to the message to
"(Binary data value not displayed)", which should give a better hint to
the person who received this error message about what was going on.
The patch also adds a new test case to BlobMemTest to force the code to
emit the 22001 message from SQLBinary, to ensure that this code path
is run in our tests.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@678769 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-962-88ccad72 | DERBY-962 Upgrade default security mechanism in client to use encrypted userid password if client can support it.
Contributed by Sunitha Kambhampati
1. If securityMechanism is explicitly specified in the connection request then client will not override it.
2. Dynamically figure out if the jvm in which the client is loaded, supports encrypted userid and
password security (EUSRIDPWD) or not and use this information to upgrade to a more secure default
security mechanism.
3. Thus if user has not specified the security mechanism, in that case the client will try to see if
it can upgrade the security mechanism and use the new upgraded security mechanism for connection to the server.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@386501 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/net/NetConnection.java",
"hunks": [
{
"added": [
" securityMechanism_ = dataSource.getSecurityMechanism(password);"
],
"header": "@@ -234,7 +234,7 @@ public class NetConnection extends org.apache.derby.client.am.Co... |
derby-DERBY-965-98f5fd95 | DERBY-965: DatabaseMetadata method supportsResultSetConcurrency
returns wrong result on network client
The DatabaseMetaData method supportsResultSetConcurrency erroneously
returns false on the network client for all arguments combination. The
embedded client returns correct results.
Patch contributed by Dag H. Wanvik <Dag.Wanvik@Sun.COM>.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@382319 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/DatabaseMetaData.java",
"hunks": [
{
"added": [
" // The stored procured will return a String containing a list",
" // of lists: For each result set type in the outer list, an",
" // inner list... |
derby-DERBY-966-4a36dabe | DERBY-435 jdbapi/checkDataSource30.java test should be changed or extended to test client DataSources
patch 2 - checkDataSource30 holdability testing for client
- Enables the checkDataSource30 test for holdability tests that are currently passing.
There appear to be several holdability bugs associated with network XA in additon to DERBY-966.
- Makes some progress toward getting checkDataSource.java to run with client, but it is not enabled yet.
- Changed to only run connection toString tests for embedded.
- Changed to only test SimpleDataSource for embedded
- Changed to perform an explicit rollback of active transactions for client before performing a PooledConnection.getConnection()
I think this is an issue with embedded that it allows a PooledConnection.getConnection() with an active transaction, instead of throwing an error if the transaction is active.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@378532 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-966-fdfc981e | DERBY-966 DERBY-1005 1) Change DRDAStatement to use the EngineConnection.prepareStatement() method that has a holdability parameter. This ensures prepares on a connection that was obtained from a XADataSource (or a ConnectionPoolDataSource) do not lose the holdability requested by the application.
2) Change the client's state of holdability to match the embedded in that a Connection's holdability is set to close cursors on commit when it has an active global XA transaction.
Patch addresses this issue completely.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@380278 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/Connection.java",
"hunks": [
{
"added": [
"import org.apache.derby.shared.common.reference.JDBC30Translation;"
],
"header": "@@ -21,6 +21,7 @@",
"removed": []
},
{
"added": [
" ... |
derby-DERBY-97-19ea3276 | DERBY-2264 (followup): Disable jdbcapi/DboPowersTest for JSR169 since
Derby does not support database encryption for that platform (per
the specification for JSR169 attached to DERBY-97).
Contributed by: Dag Wanvik (dag.wanvik@sun.com)
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@521401 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-974-efd17a12 | DERBY-974: ClientDriver can lose some connection properties
Use Properties.propertyNames() instead of Properties.keys().
Contributed by Jørgen Løland.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@587056 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-975-e4b1c442 | DERBY-975: Catch exception but don't call getMessage on it in 1.3 VMs. Fixes a canon diff in
updatableResultSet.java on ibm131.
Committed for Fernanda Pizzorno <Fernanda.Pizzorno@sun.com>
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@384061 13f79535-47bb-0310-9956-ffa450edef68
| [] |
derby-DERBY-982-63fbf423 | DERBY-982: Add genus names for network server and client to sysinfo api. Update
published api javadoc for sysinfo. Add a test of the sysinfo public api.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@422876 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/tools/org/apache/derby/tools/sysinfo.java",
"hunks": [
{
"added": [
"\t\tApache Derby embedded code in derby.jar.",
"\t\tcode in derbytools.jar",
"\t/**",
"\t *\tThe genus name for the network server code. Use this to determine the versio... |
derby-DERBY-983-f43b12c3 | DERBY-983: Remove use of Util.notImplemented(), and instead have
a client-only utility class for shorthand exceptions
Contributed by Anurag Shekhar
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@378538 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/client/org/apache/derby/client/am/CallableStatement40.java",
"hunks": [
{
"added": [],
"header": "@@ -20,7 +20,6 @@",
"removed": [
"import org.apache.derby.impl.jdbc.Util;"
]
}
]
},
{
"file": "java/client/org/apache/derby/clie... |
derby-DERBY-989-591cc35a | DERBY-989: unit/daemonService.unit fails intermittently: 'ran out of time'
Updated the javadoc for DaemonService and BasicDaemon with information about
the case where unsubscribe() is called when the client is being serviced.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@420465 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/iapi/services/daemon/DaemonService.java",
"hunks": [
{
"added": [
" performWork from time to time. The performWork method is defined by the",
"",
" <P>It is up to each <code>DaemonService</code> implementation to define i... |
derby-DERBY-989-668b59a2 | DERBY-989: unit/daemonService.unit fails intermittently: 'ran out of time'
Two test fixes (in T_DaemonService.java)
1) Clear the list of clients before each iteration of the test. This
makes the failure be exposed earlier (10 minutes instead of one
hour) because t_checkStatus() doesn't have to wait for
unsubscribed clients to be serviced.
2) Make the test accept that a client is serviced once after it has
unsubscribed. This could happen if the client is being serviced
when unsubscribe() is called.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@419479 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/unitTests/services/T_DaemonService.java",
"hunks": [
{
"added": [
"\t\t// we don't want t_checkStatus() to hang because of",
"\t\t// unsubscribed records from a previous, failed iteration",
"\t\t// (DERBY-989)",
... |
derby-DERBY-992-634980a3 | DERBY-992: A corner case bug and missing optimization in
ScrollInsensitiveResultSet
a) For a scrollable, insensitive result set (read-only) which is
empty, ResultSet#afterLast should have no effect, but erroneously
sets the internal variable afterLast to true, so that a subsequent
call to ResultSet#isAfterLast will return 'true' in the embedded
client. It does not happen on the client driver, because it seems
to do some double book-keeping for this case.
b) In ScrollInsensitiveResultSet#getNextRowCore and #getAbsoluteRow,
there are missing checks will cause unnecessary read (attempts)
from underlying result set even if end has been seen already.
Patch submitted by Dag H. Wanvik.
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@386068 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/engine/org/apache/derby/impl/sql/execute/ScrollInsensitiveResultSet.java",
"hunks": [
{
"added": [
"\t\tif (seenLast && row > lastPosition) {",
"\t\t return setAfterLastRow();",
"\t\t}\t\t",
""
],
"header": "@@ -239,6 +2... |
derby-DERBY-993-37952cfd | DERBY-993: Enable running junitTests in J2ME environments.
Committed for Myrna Van Lunteren <m.v.lunteren@gmail.com> and
Andreas Korneliussen <Andreas.Korneliussen@sun.com>
git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@387605 13f79535-47bb-0310-9956-ffa450edef68
| [
{
"file": "java/testing/org/apache/derbyTesting/functionTests/util/TestUtil.java",
"hunks": [
{
"added": [
" url += \":\" + \"user=APP;password=APP;retrieveMessagesFromServerOnGetMessage=true;\";"
],
"header": "@@ -790,7 +790,7 @@ public class T... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.