[jira] Commented: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

[ http://issues.apache.org/jira/browse/DERBY-578?page=comments#action_12416588 ] Rick Hillegas commented on DERBY-578: - Hi Manish, I'm confused about what I'm supposed to do with the latest attachment. It looks like it might just be the changes to

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416591 ] Rick Hillegas commented on DERBY-930: - I think that derby-dev should continue to discuss the issue which Olav has analyzed in DERBY-1399. I will continue this discussion

[jira] Commented: (DERBY-396) Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN

[ http://issues.apache.org/jira/browse/DERBY-396?page=comments#action_12416601 ] Rick Hillegas commented on DERBY-396: - Hi Wade, Scott did not submit a patch for this issue and he has moved on to other pursuits. This issue is currently unassigned.

[jira] Created: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

Generating derby properties on the fly can lead to non-deterministic engine startup behavior Key: DERBY-1428 URL: http://issues.apache.org/jira/browse/DERBY-1428 Project: Derby

[jira] Created: (DERBY-1429) Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly

Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly - Key: DERBY-1429 URL:

[jira] Updated: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=all ] Rick Hillegas updated DERBY-1428: - Description: A Heisenbug can arise if more than one embedded Derby application runs in the same VM and at least one of them generates derby properties on

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416775 ] Rick Hillegas commented on DERBY-930: - Adding a release note for this issue: PROBLEM If an embedded Derby application generates its own Derby properties on the fly, and

[jira] Commented: (DERBY-1429) Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly

[ http://issues.apache.org/jira/browse/DERBY-1429?page=comments#action_12416778 ] Rick Hillegas commented on DERBY-1429: -- We could separate out the booting of the engine from the registration of the embedded driver. This would eliminate this bug in

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416781 ] Rick Hillegas commented on DERBY-930: - Here is a second rev of the release note. This attempts to clarify the extra exposure introduced by jdk1.6. PROBLEM If an embedded

[jira] Commented: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

[ http://issues.apache.org/jira/browse/DERBY-578?page=comments#action_12416803 ] Rick Hillegas commented on DERBY-578: - Thanks, Manish. As you said, the fix looks pretty simple. I'm running regression tests now. I have a couple questions: 1) I don't

[jira] Commented: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=comments#action_12416810 ] Rick Hillegas commented on DERBY-1428: -- Kathey adds the following: I think DERBY-1428 and DERBY-149 are not really related to generating derby.properties on the fly

[jira] Commented: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=comments#action_12416995 ] Rick Hillegas commented on DERBY-1428: -- I think this behavior is very puzzling to the system administrator, the end-user, and tech support. What happens if a system

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_copyrights.diff Attaching derby-1271_copyrights.diff. This adjusts dates in the visible copyright notices in the user guides. Touches

[jira] Updated: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=all ] Rick Hillegas updated DERBY-1445: - Description: The task involves Adding and modifying the following methods, which were recently added by the JDBC4 expert group and which appeared in Mustang

[jira] Commented: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12417542 ] Rick Hillegas commented on DERBY-1271: -- Committed derby-1271_copyrights_v02.diff at subversion revision 416790. Release documentation for JDBC4 release

[jira] Commented: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12417821 ] Rick Hillegas commented on DERBY-1393: -- The system catalogs contain object columns, which are Formatables: sysaliases.aliasinfo syschecks.referencedcolumn

[jira] Created: (DERBY-1460) Instability in storerecovery suite when run against jar files on jdk1.6

Instability in storerecovery suite when run against jar files on jdk1.6 --- Key: DERBY-1460 URL: http://issues.apache.org/jira/browse/DERBY-1460 Project: Derby Type: Bug Components: Store

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v01.diff Knut Anders made an excellent suggestion for fixing this bug: Autoload a dummy driver which doesn't boot the engine but which

[jira] Updated: (DERBY-1460) Instability in storerecovery suite when run against jar files on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-1460?page=all ] Rick Hillegas updated DERBY-1460: - Attachment: storerecovery.zip Attaching storerecovery.zip, containing the test run directory. Instability in storerecovery suite when run against jar files

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v02.diff Attaching bug1459_v02.diff, which hopefully addresses Dan's concern. In this version the public EmbeddedDriver has a rather

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12418294 ] Rick Hillegas commented on DERBY-1459: -- Hi Kathey, With the new patch, the public interfaces should not change. Thanks for recommending those tests. I will add them to

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v03.diff Thanks for continuing to review these patches, Dan. I've attached another rev, bug1459_v03.diff. I hope this is converging on a

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v04.diff Attaching bug1159_v04.diff. This rev of the patch makes the following changes: 1) Adds a unit test (AutoloadBooting) to verify

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12420111 ] Rick Hillegas commented on DERBY-1459: -- I'm beginning to run a battery of derbyalls against this patch using various VMs with and without jar files. So far derbyall runs

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12420146 ] Rick Hillegas commented on DERBY-1459: -- Hi Kathey, Here are some answers to your questions. And don't forget to thank Knut Anders, who suggested this approach! 1) This

[jira] Resolved: (DERBY-1380) Interface changes introduced in Mustang build 86

[ http://issues.apache.org/jira/browse/DERBY-1380?page=all ] Rick Hillegas resolved DERBY-1380: -- Resolution: Fixed Interface changes introduced in Mustang build 86 Key: DERBY-1380

[jira] Closed: (DERBY-1380) Interface changes introduced in Mustang build 86

[ http://issues.apache.org/jira/browse/DERBY-1380?page=all ] Rick Hillegas closed DERBY-1380: Interface changes introduced in Mustang build 86 Key: DERBY-1380 URL:

[jira] Resolved: (DERBY-1279) Bad column name in DatabaseMetaData.getColumns()

[ http://issues.apache.org/jira/browse/DERBY-1279?page=all ] Rick Hillegas resolved DERBY-1279: -- Resolution: Fixed Fixed with DERBY-137. Bad column name in DatabaseMetaData.getColumns()

[jira] Closed: (DERBY-1279) Bad column name in DatabaseMetaData.getColumns()

[ http://issues.apache.org/jira/browse/DERBY-1279?page=all ] Rick Hillegas closed DERBY-1279: Bad column name in DatabaseMetaData.getColumns() Key: DERBY-1279 URL:

[jira] Updated: (DERBY-1483) Java Function defined with a BIGINT parameter invokes the method with a signature of method(long) rather than method(Long)

[ http://issues.apache.org/jira/browse/DERBY-1483?page=all ] Rick Hillegas updated DERBY-1483: - Component: Documentation Assigning this to Documentation component. Java Function defined with a BIGINT parameter invokes the method with a signature of

[jira] Updated: (DERBY-685) Unexpected SQL Error

[ http://issues.apache.org/jira/browse/DERBY-685?page=all ] Rick Hillegas updated DERBY-685: Component: Store Assigning this to Store component. Unexpected SQL Error Key: DERBY-685 URL:

[jira] Updated: (DERBY-607) Parameters to SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE should not be case sensitive

[ http://issues.apache.org/jira/browse/DERBY-607?page=all ] Rick Hillegas updated DERBY-607: Component: SQL Assigning this to SQL component. Parameters to SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE should not be case sensitive

[jira] Updated: (DERBY-558) Optimizer hangs with query that uses more than 6 tables and does subquery flattening.

[ http://issues.apache.org/jira/browse/DERBY-558?page=all ] Rick Hillegas updated DERBY-558: Component: SQL Assigning to SQL component. Optimizer hangs with query that uses more than 6 tables and does subquery flattening.

[jira] Updated: (DERBY-409) ClientDataSource setConnectionAttributes(create=true) fails with An attempt was made to access a database, mydbcreate=true, which was not found.

[ http://issues.apache.org/jira/browse/DERBY-409?page=all ] Rick Hillegas updated DERBY-409: Component: JDBC Assigning to JDBC component. ClientDataSource setConnectionAttributes(create=true) fails with An attempt was made to access a database,

[jira] Updated: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table Order

[ http://issues.apache.org/jira/browse/DERBY-390?page=all ] Rick Hillegas updated DERBY-390: Component: Tools Assigning to Tools component. Import/export fails with table names that are quoted in SQL like import to table Order

[jira] Updated: (DERBY-388) Intermittent failures when executing UPDATE trigger statements

[ http://issues.apache.org/jira/browse/DERBY-388?page=all ] Rick Hillegas updated DERBY-388: Component: SQL Assigning to SQL component. Intermittent failures when executing UPDATE trigger statements

[jira] Updated: (DERBY-371) Document known client/embedded differences for the Version 10.1 release

[ http://issues.apache.org/jira/browse/DERBY-371?page=all ] Rick Hillegas updated DERBY-371: Component: Documentation Assigning to Documentation component. Document known client/embedded differences for the Version 10.1 release

[jira] Updated: (DERBY-361) Unknown page format error while doing recovery after a a crash while doing in place compress.

[ http://issues.apache.org/jira/browse/DERBY-361?page=all ] Rick Hillegas updated DERBY-361: Component: Store Assigning to Store component. Unknown page format error while doing recovery after a a crash while doing in place compress.

[jira] Updated: (DERBY-309) Regression: store/backupRestore1.java fails

[ http://issues.apache.org/jira/browse/DERBY-309?page=all ] Rick Hillegas updated DERBY-309: Component: Test Assigning to Test component. Regression: store/backupRestore1.java fails --- Key:

[jira] Updated: (DERBY-308) Modify dblook to support GENERATED BY DEFAULT AS IDENTITY

[ http://issues.apache.org/jira/browse/DERBY-308?page=all ] Rick Hillegas updated DERBY-308: Component: Tools Assigning to Tools component. Modify dblook to support GENERATED BY DEFAULT AS IDENTITY

[jira] Updated: (DERBY-226) intermittent SQLException in test jdbcapi/testRelative.java

[ http://issues.apache.org/jira/browse/DERBY-226?page=all ] Rick Hillegas updated DERBY-226: Component: Test Assigning this to Test component. intermittent SQLException in test jdbcapi/testRelative.java

[jira] Updated: (DERBY-153) Bad Eclipse plugin version specification

[ http://issues.apache.org/jira/browse/DERBY-153?page=all ] Rick Hillegas updated DERBY-153: Component: Eclipse Plug-in Assigning to Eclipse-plugin component. Bad Eclipse plugin version specification

[jira] Updated: (DERBY-106) HashJoinStrategy leads to java.lang.OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-106?page=all ] Rick Hillegas updated DERBY-106: Component: SQL Assigning to SQL component. HashJoinStrategy leads to java.lang.OutOfMemoryError

[jira] Updated: (DERBY-40) Cannot set default value for BIGINT

[ http://issues.apache.org/jira/browse/DERBY-40?page=all ] Rick Hillegas updated DERBY-40: --- Component: SQL Assigning to SQL component. Cannot set default value for BIGINT --- Key: DERBY-40 URL:

[jira] Updated: (DERBY-2) Can't compile Derby on OS X

[ http://issues.apache.org/jira/browse/DERBY-2?page=all ] Rick Hillegas updated DERBY-2: -- Component: Build tools Assigning to Build Tools component. Can't compile Derby on OS X --- Key: DERBY-2 URL:

[jira] Closed: (DERBY-1398) Miscellaneous copy-editting problems in the user guides

[ http://issues.apache.org/jira/browse/DERBY-1398?page=all ] Rick Hillegas closed DERBY-1398: Miscellaneous copy-editting problems in the user guides --- Key: DERBY-1398 URL:

[jira] Closed: (DERBY-1152) Failures in sysinfo and sysinfo_withproperties induced by classpath wiring

[ http://issues.apache.org/jira/browse/DERBY-1152?page=all ] Rick Hillegas closed DERBY-1152: Failures in sysinfo and sysinfo_withproperties induced by classpath wiring --

[jira] Closed: (DERBY-937) Instability in wisconsin test

[ http://issues.apache.org/jira/browse/DERBY-937?page=all ] Rick Hillegas closed DERBY-937: --- Instability in wisconsin test - Key: DERBY-937 URL: http://issues.apache.org/jira/browse/DERBY-937

[jira] Closed: (DERBY-862) Clean up the big pile of javadoc warnings for the derbydocs target and make derbydocs run under jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-862?page=all ] Rick Hillegas closed DERBY-862: --- Clean up the big pile of javadoc warnings for the derbydocs target and make derbydocs run under jdk1.6

[jira] Closed: (DERBY-689) Various improvements to compatibility test.

[ http://issues.apache.org/jira/browse/DERBY-689?page=all ] Rick Hillegas closed DERBY-689: --- Various improvements to compatibility test. --- Key: DERBY-689 URL:

[jira] Closed: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

[ http://issues.apache.org/jira/browse/DERBY-578?page=all ] Rick Hillegas closed DERBY-578: --- Grouped select from temporary table raises null pointer exception in byte code generator

[jira] Updated: (DERBY-584) Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type

[ http://issues.apache.org/jira/browse/DERBY-584?page=all ] Rick Hillegas updated DERBY-584: Version: 10.1.1.0 Update which version this bug affects. Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type

[jira] Updated: (DERBY-565) Misleading parser diagnostics

[ http://issues.apache.org/jira/browse/DERBY-565?page=all ] Rick Hillegas updated DERBY-565: Version: 10.1.1.0 Update affects version field. Misleading parser diagnostics - Key: DERBY-565 URL:

[jira] Updated: (DERBY-625) hang in unit/cacheService.unit with wctme5.7

[ http://issues.apache.org/jira/browse/DERBY-625?page=all ] Rick Hillegas updated DERBY-625: Component: Test Assigning to Test component. hang in unit/cacheService.unit with wctme5.7 Key:

[jira] Updated: (DERBY-86) sweep of name changes to Derby

[ http://issues.apache.org/jira/browse/DERBY-86?page=all ] Rick Hillegas updated DERBY-86: --- Assigning to Unknown component. sweep of name changes to Derby -- Key: DERBY-86 URL:

[jira] Updated: (DERBY-86) sweep of name changes to Derby

[ http://issues.apache.org/jira/browse/DERBY-86?page=all ] Rick Hillegas updated DERBY-86: --- Component: Unknown Assigning to Unknown component. sweep of name changes to Derby -- Key: DERBY-86 URL:

[jira] Updated: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=all ] Rick Hillegas updated DERBY-1296: - Version: 10.2.0.0 (was: 10.1.2.1) Assigning to 10.2. Setting property derby.system.bootAll causes an Exception

[jira] Updated: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=all ] Rick Hillegas updated DERBY-1296: - Fix Version: 10.2.0.0 Version: 10.1.3.1 (was: 10.2.0.0) Setting property derby.system.bootAll causes an Exception

[jira] Updated: (DERBY-1139) Division operator may give wrong results with NUMERIC operands

[ http://issues.apache.org/jira/browse/DERBY-1139?page=all ] Rick Hillegas updated DERBY-1139: - Priority: Major (was: Critical) Downgrading the priority of this issue to Major since according to Satheesh's analysis, Derby behavior seems to be correct

[jira] Updated: (DERBY-1480) Crash with JVM 1.4.2_08-b03

[ http://issues.apache.org/jira/browse/DERBY-1480?page=all ] Rick Hillegas updated DERBY-1480: - Priority: Major (was: Blocker) Downgrading this issue to Major because it seems to be a JVM/JIT problem and not a Derby problem. Crash with JVM

[jira] Updated: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Rick Hillegas updated DERBY-936: Fix Version: 10.2.0.0 Hi Jeff and Andrew, What's the status of this issue? It would seem we need to fix this for 10.2. Main branch docs display version as

[jira] Updated: (DERBY-984) BOOLEAN Type allows illegal casts and comparisons according to SQL Spec

[ http://issues.apache.org/jira/browse/DERBY-984?page=all ] Rick Hillegas updated DERBY-984: Priority: Major (was: Blocker) Downgrading this issue to Major because it is not blocking the release, as indicated by its reassignment to 10.3. I suspect

[jira] Assigned: (DERBY-984) BOOLEAN Type allows illegal casts and comparisons according to SQL Spec

[ http://issues.apache.org/jira/browse/DERBY-984?page=all ] Rick Hillegas reassigned DERBY-984: --- Assign To: (was: Rick Hillegas) Unassigning this issue because we are uncertain about the intended release vehicle. BOOLEAN Type allows illegal

[jira] Assigned: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas reassigned DERBY-1459: Assign To: Rick Hillegas Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time

[jira] Created: (DERBY-1502) Non-deterministic behavior of lang/grantRevokeDDL.sql

Non-deterministic behavior of lang/grantRevokeDDL.sql - Key: DERBY-1502 URL: http://issues.apache.org/jira/browse/DERBY-1502 Project: Derby Type: Bug Components: Regression Test Failure Versions: 10.2.0.0

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12420955 ] Rick Hillegas commented on DERBY-1459: -- Committed at revision 421717. Derbyall ran cleanly against jar files and against the classtree on jdks 1.6, 1.5, and 1.4. The

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12421257 ] Rick Hillegas commented on DERBY-528: - I will take a look at this patch. Thanks, Francois. Support for DRDA Strong User ID and Password Substitute

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12421609 ] Rick Hillegas commented on DERBY-528: - Hi Francois, Derbyall had one error when I applied this patch: testSecMec under DerbyNet. Support for DRDA Strong User

[jira] Commented: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver

[ http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12421705 ] Rick Hillegas commented on DERBY-694: - Hi, Narayanan. Thanks for tackling this bug and for the explanatory html page. I am far from being an expert on this

[jira] Created: (DERBY-1525) Permissions-related syscat failures under DerbyNetClient on jdk1.3

Permissions-related syscat failures under DerbyNetClient on jdk1.3 -- Key: DERBY-1525 URL: http://issues.apache.org/jira/browse/DERBY-1525 Project: Derby Issue Type: Bug

[jira] Commented: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created

[ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12421739 ] Rick Hillegas commented on DERBY-1029: -- From the email thread titled Status of adding BOOLEAN-type: I have given up on re-enabling the BOOLEAN datatype in

[jira] Updated: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created

[ http://issues.apache.org/jira/browse/DERBY-1029?page=all ] Rick Hillegas updated DERBY-1029: - Attachment: derby-1029_v03.diff I am attaching a preliminary patch. This patch backs out the changes which had re-enabled the BOOLEAN datatype. I left in

[jira] Commented: (DERBY-1526) build should be able to locate the Java runtime libraries from properties not sourced from ${user.home}, but inside the current subversion checkout.

[ http://issues.apache.org/jira/browse/DERBY-1526?page=comments#action_12421874 ] Rick Hillegas commented on DERBY-1526: -- ${user.home}/ant.properties also holds configuration variables needed to run the ant-based compatibility tests. I

[jira] Created: (DERBY-1530) DatabaseMetaData.getFunctionParameters() changing name to getFunctionColumns()

DatabaseMetaData.getFunctionParameters() changing name to getFunctionColumns() -- Key: DERBY-1530 URL: http://issues.apache.org/jira/browse/DERBY-1530 Project: Derby

[jira] Updated: (DERBY-1344) Placeholder for work for 10.2 snapshots

[ http://issues.apache.org/jira/browse/DERBY-1344?page=all ] Rick Hillegas updated DERBY-1344: - Attachment: bug1344-bumplastdigit_5.diff Bumped the last digit of the release identifier after generating the 10.2.0.4 snapshot. Committed

[jira] Updated: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created

[ http://issues.apache.org/jira/browse/DERBY-1029?page=all ] Rick Hillegas updated DERBY-1029: - Attachment: derby-1029_v05.diff Hi Deepa, Thanks for bringing this to my attention. I have attached a new rev of the patch (derby-1029_v05.diff) which

[jira] Created: (DERBY-1550) procedureInTrigger has diff under jdk1.6

procedureInTrigger has diff under jdk1.6 Key: DERBY-1550 URL: http://issues.apache.org/jira/browse/DERBY-1550 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.2.0.0

[jira] Commented: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created

[ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12422447 ] Rick Hillegas commented on DERBY-1029: -- Committed derby-1029_v05.diff at subversion revision 423976. The following tests were run: 1) The script in

[jira] Commented: (DERBY-1546) Derby JDBC 4.0 driver returns 3 for JDBC driver major version

[ http://issues.apache.org/jira/browse/DERBY-1546?page=comments#action_12422464 ] Rick Hillegas commented on DERBY-1546: -- This is the correct behavior if you are running on jvm 1.4 or 1.5. If you are running on 1.6, the major version

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12422486 ] Rick Hillegas commented on DERBY-528: - I'm afraid I see a security violation when I run against the jar files. I do not see this problem when I run against the

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12422633 ] Rick Hillegas commented on DERBY-528: - I am far from being an expert on this area of the code. The changes, however, are very well commented and, coupled with

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_devGuide_v01.diff devGuide_v01.tar Attaching patch derby-1271_devGuide_v01.diff and tar of corresponding html and

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_toolsGuide_v01.diff toolsGuide_v01.tar Attaching patch derby-1271_toolsGuide_v01.diff and the correponding html and

[jira] Closed: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created

[ http://issues.apache.org/jira/browse/DERBY-1029?page=all ] Rick Hillegas closed DERBY-1029. Resolution: Fixed Backout boolean work from the 10.2 branch immediately after the branch is created

[jira] Assigned: (DERBY-887) Select statement returns wrong number of rows if you compare an integer column with a boolean expression in the where clause

[ http://issues.apache.org/jira/browse/DERBY-887?page=all ] Rick Hillegas reassigned DERBY-887: --- Assignee: (was: Rick Hillegas) Unassigning myself from this issue. We have moved out the timeframe for fixing this bug. Select statement returns

[jira] Updated: (DERBY-887) Select statement returns wrong number of rows if you compare an integer column with a boolean expression in the where clause

[ http://issues.apache.org/jira/browse/DERBY-887?page=all ] Rick Hillegas updated DERBY-887: Fix Version/s: (was: 10.3.0.0) Detaching this issue from 10.3. Fixing it seems to require changing the non-ANSI behavior of implicit and explicit casts.

[jira] Assigned: (DERBY-499) Expose BOOLEAN datatype to end users

[ http://issues.apache.org/jira/browse/DERBY-499?page=all ] Rick Hillegas reassigned DERBY-499: --- Assignee: (was: Rick Hillegas) Unassigning myself from this issue. If someone wants to tackle this in the future, please consult DERBY-1029. In order

[jira] Closed: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is ma

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas closed DERBY-1459. Resolution: Fixed Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming

[jira] Closed: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=all ] Rick Hillegas closed DERBY-930. --- Resolution: Fixed Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed, Existing Application Impact]) Closing this

[jira] Created: (DERBY-1566) Document SQLStates in 10.2

Document SQLStates in 10.2 -- Key: DERBY-1566 URL: http://issues.apache.org/jira/browse/DERBY-1566 Project: Derby Issue Type: Improvement Components: Documentation Affects Versions: 10.2.0.0

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_refGuide_v01.diff derby-1271_refGuide_v01.tar Attaching relevant changes to the Reference Guide

[jira] Assigned: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Rick Hillegas reassigned DERBY-936: --- Assignee: Rick Hillegas Main branch docs display version as 10.1, should be 10.2. -

[jira] Updated: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Rick Hillegas updated DERBY-936: Attachment: derby-936_v02.diff htmloutput.tar.gz Attaching patch derby-936_v02.diff and corresponding html output for all the documents,

[jira] Commented: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=comments#action_12423342 ] Rick Hillegas commented on DERBY-936: - The derby-936_v02.diff patch touches the following files: M src\tools\rtoolsijpropref35032.dita M

[jira] Commented: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12423353 ] Rick Hillegas commented on DERBY-1271: -- Committed derby-1271_adminGuide_v01.diff at subversion revision 425409. Release documentation for JDBC4 release

[jira] Commented: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12423355 ] Rick Hillegas commented on DERBY-1271: -- Committed derby-1271_devGuide_v01.diff at subversion revision 425410. Release documentation for JDBC4 release

[jira] Commented: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12423358 ] Rick Hillegas commented on DERBY-1271: -- Committed derby-1271_toolsGuide_v01.diff at subversion revision 425411. Release documentation for JDBC4 release

[jira] Commented: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12423362 ] Rick Hillegas commented on DERBY-1271: -- Committed derby-1271_refGuide_v01.diff at subversion revision 425417. Release documentation for JDBC4 release

[jira] Closed: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas closed DERBY-1271. Resolution: Fixed Release documentation for JDBC4 release --- Key: DERBY-1271 URL:

[jira] Commented: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=comments#action_12423377 ] Rick Hillegas commented on DERBY-936: - I don't know the answer to Dan's question. Hopefully the tech writers can field this one. It would be appealing if the

  1   2   3   4   5   6   7   8   9   10   >