| Repository |
Revision |
Date |
User |
Message |
| ASF |
#885118 |
Sat Nov 28 17:45:16 UTC 2009 |
rhillegas |
DERBY-651: Expand the UDT javadoc a bit.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/TypeId.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/UserDefinedTypeIdImpl.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/BaseTypeIdImpl.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/QueryTreeNode.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#885114 |
Sat Nov 28 17:01:17 UTC 2009 |
rhillegas |
DERBY-651: Hopefully fix an instability in UDTTest: different timestamp results on some Java platforms.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/Price.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/UDTTest.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884970 |
Fri Nov 27 19:24:13 UTC 2009 |
rhillegas |
DERBY-651: Add ability to declare UDT columns, parameters, and return values.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/UserType.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/ColumnDefinitionNode.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/TypeDescriptor.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/QueryTreeNode.java
ADD
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/Price.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/MethodCallNode.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/ErrorCodeTest.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/TypeId.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/UserDefinedTypeIdImpl.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/TypeDescriptorImpl.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/BaseTypeIdImpl.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/db2Compatibility.out
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/UDTTest.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/StaticMethodCallNode.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/catalog/types/DecimalTypeIdImpl.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884738 |
Fri Nov 27 02:28:54 UTC 2009 |
dag |
DERBY-4451 ArrayIndexOutOfBoundsException or ASSERT FAILED when inserting generated columns out of order
This patch fixes this issue as well as DERBY-4448, since they share
the same underlying problem: the former way of checking for illegal
override of generated columns in the presence of an explicit target
column list failed to look below the top level UnionNode in a table
constructor.
This specialized treatment for the case of an explicit target column
list has been removed for INSERT (it was shared with logic for
UPDATE), so checking is now done by the code for the case of no
explicit targte column list.
Backported from trunk as
svn merge -c 884163 https://svn.eu.apache.org/repos/asf/db/derby/code/trunk
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/DMLModStatementNode.java
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/InsertNode.java
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/UpdateNode.java
MODIFY
/db/derby/code/branches/10.5
MODIFY
/db/derby/code/branches/10.5/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GeneratedColumnsTest.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884616 |
Thu Nov 26 16:05:14 UTC 2009 |
kahatlen |
DERBY-4420: NullPointerException with INSERT INTO ... from EXCEPT/INTERSECT
Merged fix from trunk (revision 832379).
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/RowResultSetNode.java
MODIFY
/db/derby/code/branches/10.5/java/testing/org/apache/derbyTesting/functionTests/tests/lang/InsertTest.java
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/ResultSetNode.java
MODIFY
/db/derby/code/branches/10.5
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884542 |
Thu Nov 26 12:32:33 UTC 2009 |
kristwaa |
DERBY-4428: Add proper delete mechanism for in-memory databases
This patch adds the final pieces to enable the drop attribute for in-memory
databases. Usage: 'jdbc:derby:memory:myDB;drop=true[;user=...;password=...]'
If successful, an exception with SQL state 08006 is raised.
* EmbedConnection
Added parsing of the drop attribute. 'true' yields true, everything else
results in false (i.e. non-boolean values are accepted and silently ignored).
Added code to drop a database.
Introduced XJ048, raised when drop is combined with shutdown.
Added code to check for attribute conflicts (create, restore).
Added utility method to put the current thread to sleep.
* DatabaseContextImpl
Added a comment.
* Monitor
Added code to disallow dropping databases not using the in-memory back end.
* Attribute
Added constant for the 'drop' JDBC connection URL attribute.
* SQLState, messages.xml, lang.ErrorCodeTest
Added two new messages: 08006 (database dropped) and XJ048 (conflicting
boot attributes)
* Other tests
Enabled drop functionality and tests using it.
Patch file: DERBY-4428-2b-generic_db_drop.diff
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/shared/org/apache/derby/shared/common/reference/SQLState.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/memorydb/MemoryDbManager.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/jdbc/EmbedConnection.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/db/DatabaseContextImpl.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/services/monitor/Monitor.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/memorydb/MogTest.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/iapi/reference/Attribute.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/loc/messages.xml
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/ErrorCodeTest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/memorydb/BasicInMemoryDbTest.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884163 |
Wed Nov 25 15:57:50 UTC 2009 |
dag |
DERBY-4451 ArrayIndexOutOfBoundsException or ASSERT FAILED when inserting generated columns out of order
This patch fixes this issue as well as DERBY-4448, since they share
the same underlying problem: the former way of checking for illegal
override of generated columns in the presence of an explicit target
column list failed to look below the top level UnionNode in a table
constructor.
This specialized treatment for the case of an explicit target column
list has been removed for INSERT (it was shared with logic for
UPDATE), so checking is now done by the code for the case of no
explicit targte column list.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/DMLModStatementNode.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/UpdateNode.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/InsertNode.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GeneratedColumnsTest.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#884105 |
Wed Nov 25 14:02:17 UTC 2009 |
kristwaa |
DERBY-4428 (partial): Add proper delete mechanism for in-memory databases
Refactored code into getProtocolLeadIn()
Changed an ASSERT, as it expected equality between something that couldn't be
equal unless the default storage back end was used. It failed for the in-memory
back end, and would also fail for all other back ends. This code path hasn't
been enabled for other storage back ends before now (deleting the service root).
Patch file: DERBY-4428-3b-canonical_name_handling.diff
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#883574 |
Tue Nov 24 02:30:52 UTC 2009 |
kmarsden |
DERBY-2074 NullPointerException when two threads load sort factory concurrently
Contributed by Knut Anders Hatlen (knut dot hatlen at sun dot com)
merge 789103 from 10.5 branch
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.4/java/engine/org/apache/derby/impl/services/monitor/TopService.java
MODIFY
/db/derby/code/branches/10.4/java/testing/org/apache/derbyTesting/functionTests/tests/engine/_Suite.java
ADD
/db/derby/code/branches/10.4/java/testing/org/apache/derbyTesting/functionTests/tests/engine/ModuleLoadingTest.java
(from /db/derby/code/branches/10.5/java/testing/org/apache/derbyTesting/functionTests/tests/engine/ModuleLoadingTest.java)
MODIFY
/db/derby/code/branches/10.4/java/engine/org/apache/derby/impl/services/monitor/ModuleInstance.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#883571 |
Tue Nov 24 01:52:07 UTC 2009 |
bpendleton |
DERBY-3225: Include demo README information in demo/programs/readme.html
This change updates the README information for the demo/programs area of
the binary distribution to have additional information about the "localcal",
"scores", and "vtis" demos. These demo programs were added in DERBY-1936,
DERBY-1993, and DERBY-3129, respectively.
This change also includes the build.xml files for the "localcal" and "scores"
demos into the binary distribution.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/demo/demo.html
MODIFY
/db/derby/code/trunk/java/demo/navbar.html
MODIFY
/db/derby/code/trunk/java/demo/localcal/README
MODIFY
/db/derby/code/trunk/tools/release/build.xml
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#883397 |
Mon Nov 23 16:30:50 UTC 2009 |
bpendleton |
DERBY-711: Docs should explain that databases are platform-independent
This change adds a short paragraph to the "Introduction to Derby" page
in the Getting Started manual, explaining that the database format
used by Derby is portable and platform-independent.
|
| Files Changed |
MODIFY
/db/derby/docs/trunk/src/getstart/cgsintro.dita
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#883297 |
Mon Nov 23 10:30:30 UTC 2009 |
kristwaa |
DERBY-4428 (partial): Add proper delete mechanism for in-memory databases
Added the code required in the in-memory back end storage factory.
Some logic is required to remove the data store from the list of databases when
a database is dropped. Note that this logic isn't fully general purpose - it is
partly dependent on how the monitor / StorageFactoryService works.
Patch file: DERBY-4428-1b-in_memory_specific_delete_code.diff
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/io/vfmem/DataStore.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/io/VFMemoryStorageFactory.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#883000 |
Sat Nov 21 21:40:36 UTC 2009 |
bpendleton |
DERBY-2024: Remove JUnit utility method JDBC.vmSupportsJDBC2
Current versions of Derby require a minimum of either JDBC3 or JSR169, so
we no longer need the utility method vmSupportsJDBC2.
This change removes the unneeded method, and replaces the calls to it with
calls to vmSupportsJDBC3.
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/junit/JDBCClient.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/memory/ConnectionHandlingJunit.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/junit/TestConfiguration.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/DatabaseMetaDataTest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/VTITest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/BootAllTest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/junit/JDBC.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/UpdateXXXTest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ParameterMappingTest.java
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/AutoloadTest.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882966 |
Sat Nov 21 18:52:01 UTC 2009 |
dag |
DERBY-4450 GROUP BY in an IN-subquery inside HAVING clause whose select list is subset of group by columns, gives NPE
Patch DERBY-4450b + Knut's simplification of the autocommit call in GroupByTest#testDerby4450.
This solves the problem seen in this issue, which was a regression
from DERBY-681. The crux of the problem is that a PRN is added in the
result set tree without adjusting a higher level reference so that
wrong code is generated. The solution here is to reuse the result
column list in the inserted PRN, so that reference from above will
point correctly even after the PRN insertion (more details in JIRA).
Backported from trunk as
svn merge -c 882732 https://svn.apache.org/repos/asf/db/derby/code/trunk
plus a manual fixup.
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.5/java/engine/org/apache/derby/impl/sql/compile/SelectNode.java
MODIFY
/db/derby/code/branches/10.5/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GroupByTest.java
MODIFY
/db/derby/code/branches/10.5
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882965 |
Sat Nov 21 18:50:09 UTC 2009 |
dag |
DERBY-4450 GROUP BY in an IN-subquery inside HAVING clause whose select list is subset of group by columns, gives NPE
Patch DERBY-4450b + Knut's simplification of the autocommit call in GroupByTest#testDerby4450.
This solves the problem seen in this issue, which was a regression
from DERBY-681. The crux of the problem is that a PRN is added in the
result set tree without adjusting a higher level reference so that
wrong code is generated. The solution here is to reuse the result
column list in the inserted PRN, so that reference from above will
point correctly even after the PRN insertion (more details in JIRA).
Backported from trunk as
svn merge -c 882732 https://svn.apache.org/repos/asf/db/derby/code/trunk
plus a manual fixup.
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.4
MODIFY
/db/derby/code/branches/10.4/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GroupByTest.java
MODIFY
/db/derby/code/branches/10.4/java/engine/org/apache/derby/impl/sql/compile/SelectNode.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882958 |
Sat Nov 21 18:28:38 UTC 2009 |
dag |
DERBY-4450 GROUP BY in an IN-subquery inside HAVING clause whose select list is subset of group by columns, gives NPE
Patch DERBY-4450b + Knut's simplification of the autocommit call in GroupByTest#testDerby4450.
This solves the problem seen in this issue, which was a regression
from DERBY-681. The crux of the problem is that a PRN is added in the
result set tree without adjusting a higher level reference so that
wrong code is generated. The solution here is to reuse the result
column list in the inserted PRN, so that reference from above will
point correctly even after the PRN insertion (more details in JIRA).
Backported from trunk as
svn merge -c 882732 https://svn.apache.org/repos/asf/db/derby/code/trunk
plus a manual fixup.
|
| Files Changed |
MODIFY
/db/derby/code/branches/10.3
MODIFY
/db/derby/code/branches/10.3/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GroupByTest.java
MODIFY
/db/derby/code/branches/10.3/java/engine/org/apache/derby/impl/sql/compile/SelectNode.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882792 |
Fri Nov 20 23:47:22 UTC 2009 |
bpendleton |
DERBY-1194: Clarify wording for ways to manage the Network Server
This suggestion was contributed by Halley Pacheco de Oliveira (halleypo at gmail dot com).
This patch clarifies the description in the Derby Server and Administration
Guide regarding the different configurations of the Derby Network Server,
and how the server can be managed. Links are provided to additional
information in the Network Server section of the Derby Tutorial.
|
| Files Changed |
MODIFY
/db/derby/docs/trunk/src/adminguide/cadminconfig86869.dita
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882732 |
Fri Nov 20 21:59:47 UTC 2009 |
dag |
DERBY-4450 GROUP BY in an IN-subquery inside HAVING clause whose select list is subset of group by columns, gives NPE
Patch DERBY-4450b + Knut's simplification of the autocommit call in GrooupByTest#testDerby4450.
This solves the problem seen in this issue, which was a regression
from DERBY-681. The crux of the problem is that a PRN is added in the
result set tree without adjusting a higher level reference so that
wrong code is generated. The solution here is to reuse the result
column list in the inserted PRN, so that reference from above will
point correctly even after the PRN insertion (more details in JIRA).
|
| Files Changed |
MODIFY
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/GroupByTest.java
MODIFY
/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SelectNode.java
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882686 |
Fri Nov 20 19:13:56 UTC 2009 |
chaase3 |
DERBY-4399: Syntax description for TableViewOrFunctionExpression lacks subquery option
Modified 2 topics.
Patch: DERBY-4399-2.diff
|
| Files Changed |
MODIFY
/db/derby/docs/trunk/src/ref/rrefsqlj33215.dita
MODIFY
/db/derby/docs/trunk/src/ref/rreftableexpression.dita
|
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#882655 |
Fri Nov 20 17:56:29 UTC 2009 |
bpendleton |
DERBY-2845: Improve devguide tips on debugging deadlocks
This change adds some additional content to the Development Guide page on
debugging deadlocks. The additional content provides more information
about how to use the SYSCS_DIAG.LOCK_TABLE diagnostic table, and also
points to detailed information available in the Derby wiki.
|
| Files Changed |
MODIFY
/db/derby/docs/trunk/src/devguide/cdevconcepts50894.dita
|
