[jira] Commented: (DERBY-2547) possible NullPointerException in client/am/ProductLevel

[ https://issues.apache.org/jira/browse/DERBY-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568212#action_12568212 ] Kristian Waagan commented on DERBY-2547: Seems I just created a possible dupli

[jira] Created: (DERBY-3407) Incorrectly specifying database name with JDBC protocol causes unhelpful error message in client data sources

://issues.apache.org/jira/browse/DERBY-3407 Project: Derby Issue Type: Bug Components: JDBC, Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Priority: Minor If the database name is specified with the JDBC protocol, the user is

[jira] Updated: (DERBY-1318) Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release

[ https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-1318: --- Attachment: serialized-data-sources.zip derby-1318-1b-for_comments.stat

[jira] Updated: (DERBY-1318) Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release

[ https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-1318: --- Derby Info: (was: [Patch Available]) Fix Version/s: 10.4.0.0 Committed 'derby

[jira] Updated: (DERBY-3325) Add 'maxStatements' property to ClientConnectionPoolDataSource

[ https://issues.apache.org/jira/browse/DERBY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3325: --- Attachment: derby-3325-2a-enable_test_and_remove_workaround.diff 'derby-33

[jira] Updated: (DERBY-3325) Add 'maxStatements' property to ClientConnectionPoolDataSource

[ https://issues.apache.org/jira/browse/DERBY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3325: --- Derby Info: (was: [Patch Available]) Committed 'derby-3325-1b-maxStatements.diff'

[jira] Updated: (DERBY-3379) "No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing

[ https://issues.apache.org/jira/browse/DERBY-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3379: --- Attachment: derby-3379-1c-enforce_no_chaining.stat derby-3379-1c

[jira] Updated: (DERBY-3412) junit regression test failure on j2me in testForwardOnlyNegative(org.apache.derbyTesting.functionTests.tests.lang.ScrollCursors2Test)junit.framework.AssertionFailedError

[ https://issues.apache.org/jira/browse/DERBY-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3412: --- Attachment: derby-3412-option_b.diff That seems to be correct, and the error falls into one

[jira] Updated: (DERBY-3415) 'DataSourceSerializationTestjunit.framework.AssertionFailedError' on 'extin\ClientConnectionPoolDataSource-10_1_3_1.ser' on Windows.

[ https://issues.apache.org/jira/browse/DERBY-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3415: --- Fix Version/s: 10.4.0.0 Assignee: Kristian Waagan This is a newly added test, and

[jira] Updated: (DERBY-3415) 'DataSourceSerializationTestjunit.framework.AssertionFailedError' on 'extin\ClientConnectionPoolDataSource-10_1_3_1.ser' on Windows.

[ https://issues.apache.org/jira/browse/DERBY-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3415: --- Attachment: derby-3415-1a.diff 'derby-3415-1a.diff' adds closing of the FileI

[jira] Commented: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568959#action_12568959 ] Kristian Waagan commented on DERBY-3326: When working on this patch, I fou

[jira] Resolved: (DERBY-3415) 'DataSourceSerializationTestjunit.framework.AssertionFailedError' on 'extin\ClientConnectionPoolDataSource-10_1_3_1.ser' on Windows.

[ https://issues.apache.org/jira/browse/DERBY-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3415. Resolution: Fixed As far as I can see, the test now runs without failure on Windows

[jira] Commented: (DERBY-3299) Uniqueness violation error (23505) occurs after dropping a PK constraint if there exists a foreign key on the same columns.

[ https://issues.apache.org/jira/browse/DERBY-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569200#action_12569200 ] Kristian Waagan commented on DERBY-3299: I took 'd3299_caUtilMethods_v1.p

[jira] Updated: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

[ https://issues.apache.org/jira/browse/DERBY-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2559: --- Attachment: derby-2559-3a-documentation.diff derby-2559-2a-defenses.diff I

[jira] Updated: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

[ https://issues.apache.org/jira/browse/DERBY-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2559: --- Derby Info: [Patch Available] > recreating a datasource using javax.naming.Reference fro

[jira] Created: (DERBY-3421) Remove unused code for caching of connect bytes

Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor The client driver has code for caching connect bytes, but it is not used. This unused code clutters the rest of the code and makes it harder to understand

[jira] Updated: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3421: --- Derby Info: [Patch Available] > Remove unused code for caching of connect by

[jira] Updated: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3421: --- Attachment: derby-3421-1a-removal.stat derby-3421-1a-removal.diff '

[jira] Commented: (DERBY-3325) Add 'maxStatements' property to ClientConnectionPoolDataSource

[ https://issues.apache.org/jira/browse/DERBY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569302#action_12569302 ] Kristian Waagan commented on DERBY-3325: Committed 'derb

[jira] Updated: (DERBY-3329) Enable statement pooling in the client JDBC driver

[ https://issues.apache.org/jira/browse/DERBY-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3329: --- Attachment: derby-3329-1a-enable_statement_pooling.diff 'derby-33

[jira] Updated: (DERBY-3329) Enable statement pooling in the client JDBC driver

[ https://issues.apache.org/jira/browse/DERBY-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3329: --- Derby Info: [Patch Available] > Enable statement pooling in the client JDBC dri

[jira] Updated: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3328: --- Attachment: derby-3328-1a-extend_jdbc_objectfactories.stat derby-3328-1a

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-3a-new_classes.stat derby-3326-3a-new_classes.diff

[jira] Updated: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3328: --- Derby Info: [Patch Available] > Extend client JDBC object factory with methods to cre

[jira] Commented: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569529#action_12569529 ] Kristian Waagan commented on DERBY-3421: Tests ran fine with the patch app

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-3b-new_classes.stat derby-3326-3b-new_classes.diff

[jira] Updated: (DERBY-1318) Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release

[ https://issues.apache.org/jira/browse/DERBY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-1318: --- Attachment: derby-1318-2a-javadoc_and_build.diff 'derby-1318-2a-javadoc_and_build

[jira] Updated: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

[ https://issues.apache.org/jira/browse/DERBY-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2559: --- Attachment: derby-2559-3b-documentation.diff Thanks for looking at the patch Knut Anders

[jira] Updated: (DERBY-2559) recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails

[ https://issues.apache.org/jira/browse/DERBY-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2559: --- Derby Info: (was: [Patch Available]) Clearing patch available flag, but considering

[jira] Updated: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3421: --- Attachment: derby-3421-1b-removal.stat derby-3421-1b-removal.diff Thanks for

[jira] Resolved: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3421. Resolution: Fixed Fix Version/s: 10.4.0.0 Derby Info: (was: [Patch

[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.

[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569852#action_12569852 ] Kristian Waagan commented on DERBY-2653: Just wondering what the time frame

[jira] Commented: (DERBY-3425) J2EEDataSourceTest throws away stack trace for many errors

[ https://issues.apache.org/jira/browse/DERBY-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569896#action_12569896 ] Kristian Waagan commented on DERBY-3425: The changes look good to me.

[jira] Updated: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

[ https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3431: --- Attachment: derby-3431-1a-test_repro.diff I have not tested this with earlier releases yet

[jira] Created: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

Project: Derby Issue Type: Bug Components: JDBC, Network Client Affects Versions: 10.4.0.0 Environment: Client-server with connection pooling enabled. Reporter: Kristian Waagan Priority: Minor The connection returned from

[jira] Updated: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

[ https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3431: --- Affects Version/s: 10.1.3.1 10.2.2.0 10.3.2.1

[jira] Updated: (DERBY-1018) Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection

[ https://issues.apache.org/jira/browse/DERBY-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-1018: --- Component/s: JDBC Affects Version/s: 10.4.0.0 10.3.2.1

[jira] Commented: (DERBY-3378) Derby's timer thread should have a name that identifies it as belong to a derby instance

[ https://issues.apache.org/jira/browse/DERBY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570604#action_12570604 ] Kristian Waagan commented on DERBY-3378: Hi Serge, You are of course welcom

[jira] Reopened: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment

[ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan reopened DERBY-3306: Reopening to back out what I believe was an inappropriate change ('derby-33

[jira] Commented: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment

[ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570607#action_12570607 ] Kristian Waagan commented on DERBY-3306: Regarding Mikes comment on the 14t

[jira] Updated: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment

[ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3306: --- Attachment: derby-3306-2a-backout_and_alternative_fix.diff 'derby-33

[jira] Updated: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment

[ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3306: --- Derby Info: [Patch Available] > jdbc4.StatementEventsTest cannot be run individually i

[jira] Commented: (DERBY-3412) junit regression test failure on j2me in testForwardOnlyNegative(org.apache.derbyTesting.functionTests.tests.lang.ScrollCursors2Test)junit.framework.AssertionFailedErro

[ https://issues.apache.org/jira/browse/DERBY-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570611#action_12570611 ] Kristian Waagan commented on DERBY-3412: I have decided to go for options a a

[jira] Created: (DERBY-3438) Allow SQL query text to be null in StatementKey

Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Fix For: 10.4.0.0 Because the SQL isn't checked before the cache is queried, StatementKey should allow the SQL query text to be null. This simpl

[jira] Updated: (DERBY-3438) Allow SQL query text to be null in StatementKey

[ https://issues.apache.org/jira/browse/DERBY-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3438: --- Attachment: derby-3438-1a-allow_sql_null.diff 'derby-3438-1a-allow_sql_null.diff&#

[jira] Created: (DERBY-3440) Run suites.All with statement pooling enabled and classify the problems occurring

Issue Type: Sub-task Components: Test Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Fix For: 10.4.0.0 The patches for the statement pooling feature should soon make it possible

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-3c-new_classes.diff 'derby-3326-3c-new_classes.diff' con

[jira] Created: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

/jira/browse/DERBY-3441 Project: Derby Issue Type: Sub-task Components: JDBC, Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Fix For: 10.4.0.0 Initial investigations indicate there are no existing suitable methods

[jira] Commented: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570799#action_12570799 ] Kristian Waagan commented on DERBY-3441: The ones you mention are not too h

[jira] Commented: (DERBY-3192) Cache session data in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570990#action_12570990 ] Kristian Waagan commented on DERBY-3192: I had a quick look at the patch (mark

[jira] Commented: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570995#action_12570995 ] Kristian Waagan commented on DERBY-3328: Committed 'derb

[jira] Updated: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3328: --- Derby Info: (was: [Patch Available]) > Extend client JDBC object factory with methods

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: (was: [Patch Available]) Committed 'derby-3326-2a-method_rename.diff'

[jira] Commented: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570994#action_12570994 ] Kristian Waagan commented on DERBY-3326: Committed 'derby-3326-3c-new_cla

[jira] Resolved: (DERBY-3306) jdbc4.StatementEventsTest cannot be run individually in a clean environment

[ https://issues.apache.org/jira/browse/DERBY-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3306. Resolution: Fixed Derby Info: (was: [Patch Available]) Committed 'derby-33

[jira] Updated: (DERBY-3412) junit regression test failure on j2me in testForwardOnlyNegative(org.apache.derbyTesting.functionTests.tests.lang.ScrollCursors2Test)junit.framework.AssertionFailedError

[ https://issues.apache.org/jira/browse/DERBY-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3412: --- Assignee: Kristian Waagan I expect the patch committed for DERBY-3306 (revsion 629894) to

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-4a-cpdsc_shutEngine.diff 'derby-3326-4a-cpdsc_shutEngine

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: [Patch Available] The small patch 'derby-3326-4a-cpdsc_shutEngine.diff'

[jira] Created: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

Project: Derby Issue Type: Task Components: JDBC, Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Fix For: 10.4.0.0 ResultSet.getStatement must return the

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Attachment: derby-3446-1a_rs_getstatement.stat derby-3446

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Derby Info: [Patch Available] Patch 1a ready for review. > Make ResultSet.getState

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Attachment: derby-3446-2a_rs_getstatement_alternative.stat derby-3446

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Attachment: derby-3446-2b_rs_getstatement_alternative.diff Attached 'derby

[jira] Resolved: (DERBY-3309) Minor cleanups in ClientPooledConnection40 and ClientPooledConnection

[ https://issues.apache.org/jira/browse/DERBY-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3309. Resolution: Fixed Fix Version/s: 10.3.2.2 10.2.2.1 Merged

[jira] Closed: (DERBY-3325) Add 'maxStatements' property to ClientConnectionPoolDataSource

[ https://issues.apache.org/jira/browse/DERBY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3325. -- Resolution: Fixed Closing. Further work, if any, will be handled as separate JIRAs. >

[jira] Created: (DERBY-3457) Closing a logical connection must close all assoicated logical statements

Type: Task Components: JDBC, Network Client Affects Versions: 10.4.0.0 Environment: Client-server with statement pooling enabled in the client driver. Reporter: Kristian Waagan Assignee: Kristian Waagan Fix For: 10.4.0.0 When a logical

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Summary: Closing a logical connection must close all associated logical statements (was

[jira] Updated: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3328: --- Attachment: derby-3328-2a-change_signatures.stat derby-3328-2a

[jira] Commented: (DERBY-3328) Extend client JDBC object factory with methods to create objects required for statement pooling

[ https://issues.apache.org/jira/browse/DERBY-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571779#action_12571779 ] Kristian Waagan commented on DERBY-3328: Committed 'derb

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-5a-enable_logicalstmtentity_pptest.diff Attached 'derby-33

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Attachment: derby-3457-1a-stmt_closing.stat derby-3457-1a-stmt_closing.diff

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Derby Info: [Patch Available] > Closing a logical connection must close all associa

[jira] Commented: (DERBY-3451) Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.

[ https://issues.apache.org/jira/browse/DERBY-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572025#action_12572025 ] Kristian Waagan commented on DERBY-3451: BTW, I ran the regression tests with

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Derby Info: (was: [Patch Available]) > Make ResultSet.getStatemet return the corr

[jira] Updated: (DERBY-3446) Make ResultSet.getStatemet return the correct statement when created by a logical statement

[ https://issues.apache.org/jira/browse/DERBY-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3446: --- Attachment: derby-3446-2c_rs_getstatement_alternative.diff Attached 'derby

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: (was: [Patch Available]) Committed 'derby-3326-4a-cpdsc_shutEngine.dif

[jira] Updated: (DERBY-3469) Clob.length() doesn't detect a closed underlying connection in a consistent way

[ https://issues.apache.org/jira/browse/DERBY-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3469: --- Attachment: ClosedClobTest.java Attached a very simple repro ('ClosedClobTest.java'

[jira] Created: (DERBY-3469) Clob.length() doesn't detect a closed underlying connection in a consistent way

Derby Issue Type: Bug Components: JDBC, Network Client Affects Versions: 10.3.2.1, 10.4.0.0 Environment: Client-driver Reporter: Kristian Waagan Priority: Minor Depending on the state of the Clob, the method length gives two different SQL states

[jira] Updated: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2667: --- Attachment: derby-2667-WriteExceptionsToFileAsTheyHappen.diff 'derby

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572460#action_12572460 ] Kristian Waagan commented on DERBY-3465: I also tried to reproduce this, wit

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572461#action_12572461 ] Kristian Waagan commented on DERBY-2667: Well, maybe I misunderstood, but if

[jira] Closed: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3421. -- > Remove unused code for caching of connect by

[jira] Closed: (DERBY-3357) Reduce runtime of jdbcapi.DataSourceTest

[ https://issues.apache.org/jira/browse/DERBY-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3357. -- Refactorings seems to be working fine, and I don't expect more work to be done. Closing

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Derby Info: [Patch Available] > 'testNetworkServerSecurityMechanism

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Attachment: derby-3465-1a-remove_try_catch.diff 'derby-3465-1a-remove_try_catch

[jira] Resolved: (DERBY-3438) Allow SQL query text to be null in StatementKey

[ https://issues.apache.org/jira/browse/DERBY-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3438. Resolution: Fixed Committed 'derby-3438-1a-allow_sql_null.diff' to trunk wit

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572496#action_12572496 ] Kristian Waagan commented on DERBY-2667: Dag, it is a valid concern and I have

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-6a-npe_fix_synch_CLC.diff 'derby-3326-6a-npe_fix_synch_CLC

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-6b-npe_fix_synch_CLC.diff 'derby-3326-6b-npe_fix_synch_CLC

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Attachment: derby-3457-1b-stmt_closing.diff 'derby-3457-1b-stmt_closing.diff' is a

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572552#action_12572552 ] Kristian Waagan commented on DERBY-3465: Thank you for the review Dag. The

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Description: http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/testlog/SunOS

[jira] Updated: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3441: --- Derby Info: [Patch Available] Assignee: Kristian Waagan > Determine and implemen

[jira] Updated: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3441: --- Attachment: derby-3441-1a-statement_reset.diff 'derby-3441-1a-statement_reset.diff&#x

[jira] Updated: (DERBY-3440) Run suites.All with statement pooling enabled and classify the problems occurring

[ https://issues.apache.org/jira/browse/DERBY-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3440: --- Attachment: WithCPDS-WithStatementPooling-errors-01.txt WithCPDS

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: [Patch Available] > Introduce a caching logical connection and logical prepa

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-7a-prepare_column_indexes_names_fix.diff 'derby-33

[jira] Updated: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3441: --- Attachment: derby-3441-2a-minor_am_refactoring.diff Thanks for the comment Dan. I'll ad

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: (was: [Patch Available]) Committed 'derby-33

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Attachment: derby-3457-2a-stmt_registration.diff 'derby-3457-2a-stmt_registration.diff&

<    10   11   12   13   14   15   16   17   18   19   >