[jira] Updated: (DERBY-974) ClientDriver can lose some connection properties

[ https://issues.apache.org/jira/browse/DERBY-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-974: Attachment: derby-974-3.diff Changed test to the original plan of using create=true as a default in

[jira] Updated: (DERBY-974) ClientDriver can lose some connection properties

[ https://issues.apache.org/jira/browse/DERBY-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-974: Attachment: (was: derby-974-3.diff) ClientDriver can lose some connection properties

[jira] Updated: (DERBY-974) ClientDriver can lose some connection properties

[ https://issues.apache.org/jira/browse/DERBY-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-974: Attachment: derby-974-3.diff ... now with correct indentation ClientDriver can lose some

[jira] Commented: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536590 ] John H. Embretsen commented on DERBY-2914: -- I believe Kim is right about factors in the default connection

[jira] Updated: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-2065: - Attachment: releaseNote.html Network and embedded difference in SQLSTATE and message when

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536591 ] Jørgen Løland commented on DERBY-2065: -- Release note attached. Network and embedded difference in SQLSTATE

[jira] Issue Comment Edited: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536590 ] johnemb edited comment on DERBY-2914 at 10/22/07 12:59 AM: - I believe Kim is

Re: code coverage for junit tests for svn 10.3 revision 579033

As far as I can see, code coverage has improved by about 8% for classes, 10% for methods, 12% for blocks, and 13% for lines since last run for svn trunk revision 529822. This is great! And thanks for running this! Ramandeep Kaur wrote: Hi, I ran code coverage for junit tests for svn 10.3

[jira] Resolved: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-3093. --- Resolution: Fixed Fix Version/s: 10.2.2.1 Committed to 10.2 with revision

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536601 ] Dag H. Wanvik commented on DERBY-2065: -- Committed patch derby-2065_1 at svn 587040. I added this note to the

[jira] Commented: (DERBY-3130) Reduce memory footprint of StoredRecordHeader

[ https://issues.apache.org/jira/browse/DERBY-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536603 ] Kristian Waagan commented on DERBY-3130: I ran the patch with the load I experience problems with, and it

[jira] Issue Comment Edited: (DERBY-3130) Reduce memory footprint of StoredRecordHeader

[ https://issues.apache.org/jira/browse/DERBY-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536603 ] kristwaa edited comment on DERBY-3130 at 10/22/07 2:12 AM: -- I ran the patch with

[jira] Updated: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-2065: - Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed,

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536605 ] Dag H. Wanvik commented on DERBY-2065: -- Thanks for the release note, Jørgen! Looks good, some comments!

Re: What is the command to check out the 10.3 branch?

It is probably worth noting that you can find out the exact URL to a particular part of the repository by browsing to it, for example by starting at https://svn.apache.org/repos/asf/db/derby/ in a web browser. This is also a useful way to get to know the structure of our repository (the same

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536608 ] Knut Anders Hatlen commented on DERBY-2065: --- SQLStateConstants.INVALID_TRANSACTION_STATE_NO_SUBCLASS are

[jira] Commented: (DERBY-2188) Developer's Guide talks about a jdbc url property locale which is not supported by Derby.

[ https://issues.apache.org/jira/browse/DERBY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536609 ] Dag H. Wanvik commented on DERBY-2188: -- The reference i mentioned in rgsquck30197.html is still wrong: One or

[jira] Updated: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-2998: -- Attachment: row_number_prototype-2c.stat row_number_prototype-2c.diff After

[jira] Updated: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-2998: -- Attachment: (was: row_number_prototype-2b.diff) Add support for ROW_NUMBER() window

[jira] Commented: (DERBY-974) ClientDriver can lose some connection properties

[ https://issues.apache.org/jira/browse/DERBY-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536628 ] Knut Anders Hatlen commented on DERBY-974: -- Thanks Jørgen! Now I see that the test fails without the fix and

[jira] Resolved: (DERBY-974) ClientDriver can lose some connection properties

[ https://issues.apache.org/jira/browse/DERBY-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-974. -- Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.1.5

Re: code coverage for junit tests for svn 10.3 revision 579033

Ramandeep Kaur [EMAIL PROTECTED] writes: Hi, I ran code coverage for junit tests for svn 10.3 revision 579033 with sun jdk142, sun jdk15, and sun jdk16. Here are the code coverage results: Are the underlying data available somewhere? Just curious to see some of that which is not covered..

Re: code coverage for junit tests for svn 10.3 revision 579033

Andrew usually puts this under http://people.apache.org/~fuzzylogic/codecoverage/, but this has not been done yet for this run. Dag H. Wanvik wrote: Ramandeep Kaur [EMAIL PROTECTED] writes: Hi, I ran code coverage for junit tests for svn 10.3 revision 579033 with sun jdk142, sun jdk15,

[jira] Updated: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-2065: - Attachment: releaseNote.html Good suggestions, Dag. Incorporated in the latest releaseNote.html

max size of authentication ids: lift restriction?

Hi, While working on roles, I notice that there is a max size of 30 on user ids in derby (authentication identifiers), e.g. the check being performed in the parser: private void checkAuthorizationLength( String authorization) : checkIdentifierLengthLimit( authorization,

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536650 ] Dag H. Wanvik commented on DERBY-2065: -- Knut, I admit I was of two minds about leaving the message, for the

[jira] Commented: (DERBY-3130) Reduce memory footprint of StoredRecordHeader

[ https://issues.apache.org/jira/browse/DERBY-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536651 ] Knut Anders Hatlen commented on DERBY-3130: --- Thanks for testing the patch, Kristian. I'm glad it solved

[jira] Commented: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

[ https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536652 ] Dag H. Wanvik commented on DERBY-2065: -- Thanks for the revision, Jørgen! I think the release notes look good

Re: Cache session data in the client driver?

[EMAIL PROTECTED] (Dag H. Wanvik) writes: [EMAIL PROTECTED] writes: For the second option I was wondering if it would be possible to use the EXCSQLSET trick that Øyvind used for setQueryTimeout, in reverse. According to the DRDA spec (v4, volume 3, page 359-360) it is possible to add one or

[jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536670 ] Thomas Nielsen commented on DERBY-2998: --- Here's how it seems to work for indexes for the following simple

[jira] Issue Comment Edited: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536670 ] thomanie edited comment on DERBY-2998 at 10/22/07 6:49 AM: - Here's how it seems to

[jira] Commented: (DERBY-3071) Replication: Modify logging subsystem for slave replication mode

[ https://issues.apache.org/jira/browse/DERBY-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536690 ] Øystein Grøvlen commented on DERBY-3071: Thanks for the patch, Jørgen. My review of this patch are more

[jira] Commented: (DERBY-2911) Implement a buffer manager using java.util.concurrent classes

[ https://issues.apache.org/jira/browse/DERBY-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536700 ] Knut Anders Hatlen commented on DERBY-2911: --- I have not implemented a background cleaner for the new

[jira] Reopened: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik reopened DERBY-3073: -- Reopening this issue to add a follow-up patch. SQL roles: add parser support

[jira] Commented: (DERBY-2967) Single character does not match high value unicode character with collation TERRITORY_BASED

[ https://issues.apache.org/jira/browse/DERBY-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536705 ] Knut Anders Hatlen commented on DERBY-2967: --- When you said even though 'aa' = 'å' in Norwegian territory,

[jira] Updated: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3073: - Attachment: DERBY-3073-part-2.diff This small patch, DERBY-3073-part-2, adds the following to

[jira] Updated: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3073: - Derby Info: [Patch Available, Existing Application Impact, Release Note Needed] (was: [Release

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (19 issues) Subscriber: derby-dev Key Summary DERBY-3073 SQL roles: add parser support https://issues.apache.org/jira/browse/DERBY-3073 DERBY-2967 Single character does not match high value unicode character

Regression Test Report - Daily 586912 - Sun DBTG

[Auto-generated mail] *Daily* 586912/2007-10-21 18:00:11 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0288288 072.97% derbyall 097119711 0 1135.14% suitesAll sles 1

[jira] Commented: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536722 ] Daniel John Debrunner commented on DERBY-3093: -- I'm close to -1 on this patch, it introduces a single

Regarding DERBY-1272

Hello In writing test for DERBY-1272, I receive the following exception 1)testDerbyLog(org.apache.derbyTesting.functionTests.tests.lang.DerbyLogTest)java.security.AccessControlException: access denied (java.util.PropertyPermission derby.system.home read) and the reason is because I am trying to

[jira] Commented: (DERBY-3140) InListMultiProbeTest creates 30000 DataRow objects that do not get released during suites.All run

[ https://issues.apache.org/jira/browse/DERBY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536727 ] Kathey Marsden commented on DERBY-3140: --- Kristian Waagan said: I guess this also means that larger data

Re: Regarding DERBY-1272

Hi Ramin, The problem may be that your test is not reading derby.system.home from inside a privileged block. If your test extends BaseTestCase, then you can call getSystemProperty() to read derby.system.home and that method will set up the privileged block needed to read the property. Hope

[jira] Closed: (DERBY-3140) InListMultiProbeTest creates 30000 DataRow objects that do not get released during suites.All run

[ https://issues.apache.org/jira/browse/DERBY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-3140. - Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.1.5

[jira] Updated: (DERBY-2212) Add Unique where not null to create index

[ https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2212: -- No, I don't think you have overlooked a compatibility issue. But you do recogonize there is a

[jira] Commented: (DERBY-3140) InListMultiProbeTest creates 30000 DataRow objects that do not get released during suites.All run

[ https://issues.apache.org/jira/browse/DERBY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536749 ] Kathey Marsden commented on DERBY-3140: --- I found this blog that might be of interest:

[jira] Updated: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3138: - Attachment: derby-3138-fix-aa.diff Attaching a fix for this bug, derby-31380-fix-aa.diff.

[jira] Updated: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3138: - Derby Info: [Patch Available, Regression] (was: [Regression]) Optimizer error when vtis are

[jira] Commented: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536759 ] Rick Hillegas commented on DERBY-3073: -- Hi Dag, Looks uncontroversial to me. +1. SQL roles: add parser

[jira] Commented: (DERBY-2967) Single character does not match high value unicode character with collation TERRITORY_BASED

[ https://issues.apache.org/jira/browse/DERBY-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536768 ] Mamta A. Satoor commented on DERBY-2967: Knut, yes, I did mean the SQL = operation. Also, thanks for your

[jira] Commented: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536770 ] Knut Anders Hatlen commented on DERBY-3093: --- Isn't this a cost that you only get when you prepare a

[jira] Commented: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536782 ] Daniel John Debrunner commented on DERBY-3093: -- No, this is an execution time cost for every statement.

[jira] Commented: (DERBY-2967) Single character does not match high value unicode character with collation TERRITORY_BASED

[ https://issues.apache.org/jira/browse/DERBY-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536792 ] Knut Anders Hatlen commented on DERBY-2967: --- Thanks Mamta, that makes sense. I am wondering if anyone

[jira] Reopened: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen reopened DERBY-3093: --- Thanks Dan. In that case I agree that this should be addressed before the issue is

[jira] Updated: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart updated DERBY-2914: - Derby Info: [Patch Available] new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS,

[jira] Updated: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart updated DERBY-2914: - Attachment: rrefsetuseraccess.html rrefgetuseraccess.html

building osgi support

Right now, the osgi support is an optional part of the Derby build. I think this is because people used to have to click through a license agreement in order to download the osgi jarball which Derby needed to compile this support. However, it appears to me that this jarball is now available

JUnit memory consumption

Upon more research it seems that JUnit creates one instance of each test class per fixture and keeps that reference until the end of the suites.All run. That means any state in the test hangs around as well, which slowly adds up as the test runs. This is particularly problematic for tests

[jira] Updated: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3093: -- Given dan's observation will this be backed out of the branches until the correct fix is

[jira] Commented: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536820 ] Rick Hillegas commented on DERBY-3138: -- Committed derby-3138-fix-aa.diff at subversion revision 587230.

[jira] Updated: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3138: - Derby Info: [Regression] (was: [Regression, Patch Available]) Optimizer error when vtis are

[jira] Resolved: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-3138. -- Resolution: Fixed Optimizer error when vtis are invoked with correlated references to outer

backporting changes to branches

Remember that the point of the branch is to provide a stable always working set of code that anyone can take and make either a public release of or expect that a private release will work. So only bug fixes should go in, and when I act as a committer I usually exercise more caution when

[jira] Commented: (DERBY-2188) Developer's Guide talks about a jdbc url property locale which is not supported by Derby.

[ https://issues.apache.org/jira/browse/DERBY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536821 ] Laura Stewart commented on DERBY-2188: -- In the file derby.ui.codeset property in the Derby Tools and Utilities

[jira] Updated: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart updated DERBY-2914: - Attachment: derby2914_4.diff new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS,

Re: building osgi support

Rick Hillegas wrote: Right now, the osgi support is an optional part of the Derby build. I think this is because people used to have to click through a license agreement in order to download the osgi jarball which Derby needed to compile this support. However, it appears to me that this

[jira] Commented: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536832 ] Kim Haase commented on DERBY-2914: -- They look great to me, Laura. new stored procedures,

[jira] Commented: (DERBY-1670) Remove optional osgi.jar download by including equivalent jar from the apache incubator felix project in the Derby's svn

[ https://issues.apache.org/jira/browse/DERBY-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536838 ] Rick Hillegas commented on DERBY-1670: -- Felix has graduated from the incubator. I think that means that the IP

[jira] Updated: (DERBY-716) Re-enable VTIs

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-716: Attachment: derby-716-11-subqueries-aa.diff Attaching derby-716-11-subqueries-aa.diff. This adds a

[jira] Commented: (DERBY-1670) Remove optional osgi.jar download by including equivalent jar from the apache incubator felix project in the Derby's svn

[ https://issues.apache.org/jira/browse/DERBY-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536843 ] Daniel John Debrunner commented on DERBY-1670: -- I don't think we add anything to the NOTICE file since

[jira] Commented: (DERBY-1823) Derby Developer's Guide - Issues w/ User authentication and authorization extended examples section/paragraph

[ https://issues.apache.org/jira/browse/DERBY-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536870 ] Francois Orsini commented on DERBY-1823: Great changes Kim. I tested all the samples and they worked great.

[jira] Commented: (DERBY-3093) Intermittent transaction failure caused by internal duplicate savepoint name for triggers

[ https://issues.apache.org/jira/browse/DERBY-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536873 ] James F. Adams commented on DERBY-3093: --- I will attempt to make the necessary changes. In looking a bit

[jira] Commented: (DERBY-2352) Assertion Failure with order by and group by expression

[ https://issues.apache.org/jira/browse/DERBY-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536899 ] Bryan Pendleton commented on DERBY-2352: A naive attempt to use other data types in the repro script via

[jira] Commented: (DERBY-2352) Assertion Failure with order by and group by expression

[ https://issues.apache.org/jira/browse/DERBY-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536900 ] Bryan Pendleton commented on DERBY-2352: LTRIM and TRIM (TRAILING) don't obviously suffer from the same

[jira] Created: (DERBY-3143) testPositionClobWithUnicode in tests.jdbcapi.BlobClob4BlobTest is failing on IBM142 with Log Record has been sent to the stream, but it cannot be applied to the store (Ob

testPositionClobWithUnicode in tests.jdbcapi.BlobClob4BlobTest is failing on IBM142 with Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also.