[jira] Commented: (DERBY-1825) Errors 2850A,2850G,28508 are similar - can be combined into a single message.

[ https://issues.apache.org/jira/browse/DERBY-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489313 ] Jørgen Løland commented on DERBY-1825: -- I have looked into all the '28'-error messages. I suggest that the follo

Re: is anyone looking at new import/export tinderbox errors that look like they started with checkin for DERBY-2193 or DERBY-2444?

As Indicated in the comments of Derby-2444 I have run derbyall and junit.All before submitting this patch and I did not have any import related failures. Also the following is the list of files 2444 modifies as can be found from the .stat files attached to this issue (hopefully this will help

Re: how should store get an object based on format id and collation id?

Daniel John Debrunner wrote: Mike Matrigali wrote: I'd assumed that every time a collation was needed that enough meta data was available to determine the collation. For example with language based comparisons the collation will be known at compile time and thus can be used. For index b

Re: how should store get an object based on format id and collation id?

Daniel John Debrunner wrote: Mike Matrigali wrote: Daniel John Debrunner wrote: Mamta Satoor wrote: I spent some time on points 1(using Monitor to get dvd directly) and 3(optimized allocation, caching some of the work.) which requires us to solve the problem of how to get the InstanceG

[jira] Created: (DERBY-2554) convert lang/supersimple.sql to JUnit

convert lang/supersimple.sql to JUnit - Key: DERBY-2554 URL: https://issues.apache.org/jira/browse/DERBY-2554 Project: Derby Issue Type: Task Components: Test Reporter: Kathey Marsden

[jira] Updated: (DERBY-2517) convert lang/forupdate.sql to junit

[ https://issues.apache.org/jira/browse/DERBY-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramandeep Kaur updated DERBY-2517: -- Derby Info: [Patch Available] > convert lang/forupdate.sql to junit >

[jira] Updated: (DERBY-2517) convert lang/forupdate.sql to junit

[ https://issues.apache.org/jira/browse/DERBY-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramandeep Kaur updated DERBY-2517: -- Attachment: DERBY-2517.diff I am attaching patch for conversion of forupdate.sql to junit test

[jira] Commented: (DERBY-2542) convert lang/scrollCursors1.sql to junit

[ https://issues.apache.org/jira/browse/DERBY-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489262 ] Kathey Marsden commented on DERBY-2542: --- scrollCursors3.sql was also converted with this issue. > convert lan

[jira] Closed: (DERBY-2542) convert lang/scrollCursors1.sql to junit

[ https://issues.apache.org/jira/browse/DERBY-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-2542. - > convert lang/scrollCursors1.sql to junit > - > >

[jira] Resolved: (DERBY-2542) convert lang/scrollCursors1.sql to junit

[ https://issues.apache.org/jira/browse/DERBY-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden resolved DERBY-2542. --- Resolution: Fixed > convert lang/scrollCursors1.sql to junit > -

[jira] Created: (DERBY-2553) values SYSCS_UTIL.SYSCS_GET_RUNTIMESTATISTICS() returns null in test ScrollCursors1Test when run against network server

values SYSCS_UTIL.SYSCS_GET_RUNTIMESTATISTICS() returns null in test ScrollCursors1Test when run against network server Key: DERBY-2553 URL:

Re: how should store get an object based on format id and collation id?

Mike Matrigali wrote: Daniel John Debrunner wrote: Mamta Satoor wrote: I spent some time on points 1(using Monitor to get dvd directly) and 3(optimized allocation, caching some of the work.) which requires us to solve the problem of how to get the InstanceGetter to return the correct DVD f

Re: how should store get an object based on format id and collation id?

Mike Matrigali wrote: Ok, this answers a previous question I had posted. Store currently uses the following to get new "empty" instances of classes which will subsequently be initiated by calls to readExternal(): dvd = dvd.getClass().newInstance() It sounds like this should be replaced by: dvd

[jira] Updated: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olav Sandstaa updated DERBY-2020: - Attachment: jvmsyncbug_v3.stat jvmsyncbug_v3.diff This patch includes changes bas

Re: how should store get an object based on format id and collation id?

OK, I think I understand what Dan is suggesting here. Dan, let me know if I am off. Keep the InstanceGetter as it is right now. There will be a new interface on DVF called getNewInstance(format id, collation id). This new interface will use the code similar to code in BaseMonitor.classFromIdentif

In TypeDescriptorImpl, collationDerivation probably should default to "implicit" rather than "none".

Hi, There was some discussion earlier about setting TypeDescriptorImpl's collationDerivation field to StringDataValue.COLLATION_DERIVATION_NONE(which in SQL Spec language means none). I can dig that mail out if anyone needs it for the background information. While working on language based order

[jira] Commented: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489241 ] Olav Sandstaa commented on DERBY-2020: -- Thanks for comments, Suresh. 1) The reason for creating a new file "rw

[jira] Reopened: (DERBY-2373) Upgrade documentation PDF builds to use FOP .93

[ https://issues.apache.org/jira/browse/DERBY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reopened DERBY-2373: -- I think there may be something not quite right about the way this new version of FOP is working with our t

Re: how should store get an object based on format id and collation id?

Daniel John Debrunner wrote: Mike Matrigali wrote: Daniel John Debrunner wrote: Mamta Satoor wrote: Hi Dan, The problem we are trying to solve is provide a way to Store so that it can call a method (say it's called getInstanceGetterForFormatIDandCollationType) on DVF with format id

[jira] Commented: (DERBY-827) Performance can be improved by re-using language ResultSets across Activation executions.

[ https://issues.apache.org/jira/browse/DERBY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489224 ] Daniel John Debrunner commented on DERBY-827: - If the statement is being re-compiled how is it picking up

Re: how should store get an object based on format id and collation id?

Mike Matrigali wrote: Daniel John Debrunner wrote: Mamta Satoor wrote: Hi Dan, The problem we are trying to solve is provide a way to Store so that it can call a method (say it's called getInstanceGetterForFormatIDandCollationType) on DVF with format id & collation type and get an Insta

[jira] Resolved: (DERBY-2541) Create initial testing framework for Junit Collation testing

[ https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden resolved DERBY-2541. --- Resolution: Fixed Derby Info: (was: [Patch Available]) > Create initial testing framewo

[jira] Closed: (DERBY-2541) Create initial testing framework for Junit Collation testing

[ https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-2541. - > Create initial testing framework for Junit Collation testing >

Regression Test Report - tinderbox_trunk16 529292 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 529292/2007-04-16 17:42:43 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0346346 096.85% derbyall F:8,E:073957387 0

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

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489204 ] Rick Hillegas commented on DERBY-716: - Thanks for your feedback, Dan and Christian. I agree that ResultSet has be

[jira] Commented: (DERBY-2541) Create initial testing framework for Junit Collation testing

[ https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489200 ] Kathey Marsden commented on DERBY-2541: --- I believe they are all created within the same Derby system. > Cre

[jira] Commented: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.

[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489198 ] A B commented on DERBY-2538: The version 4 changes look good to me. +1 to commit pending resolution of DERBY-2488. Tha

[jira] Commented: (DERBY-2541) Create initial testing framework for Junit Collation testing

[ https://issues.apache.org/jira/browse/DERBY-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489196 ] Mamta A. Satoor commented on DERBY-2541: Kathey, I reviewed the patch from a functionality point of view (and

[jira] Updated: (DERBY-2346) Provide set methods for clob for embedded driver

[ https://issues.apache.org/jira/browse/DERBY-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-2346: -- Attachment: derby-2346v2.diff description of derby-2346v2.diff changes from previous patch 1.

Re: Question about grant/revoke

Dyre, my memory has gone rusty on this topic but what I seem to recollect is not everything dependent on table will also be dependent for TablePermsDescr too. This is because say the table owner creates a view on that table, then no TablePermsDescr is required by such a view but that view will dep

[jira] Closed: (DERBY-1516) Inconsistent behavior for getBytes and getSubString for embedded versus network

[ https://issues.apache.org/jira/browse/DERBY-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell closed DERBY-1516. > Inconsistent behavior for getBytes and getSubString for embedded versus > network >

Re: Question about grant/revoke

Mamta Satoor <[EMAIL PROTECTED]> writes: > When a revoke is issued, Derby sends an > DependencyManager.REVOKE_PRIVILEGEinvalidation to dependents of the > privilege being revoked. Hmm, I've added some trace, and as far as I can tell, the only Provider that gets DependencyManager.REVOKE_PRIVILEGE

[jira] Updated: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.

[ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-2538: - Attachment: DERBY-2538-4.zip DERBY-2538-4.diff Attaching DERBY-2538-4.diff and DERBY-2538

Re: is anyone looking at new import/export tinderbox errors that look like they started with checkin for DERBY-2193 or DERBY-2444?

Hopefully, revision 529322 fixes this regression. See DERBY-2193 for more information. Regards, -Rick Rick Hillegas wrote: Hi Mike, I will take a look at this. At first blush, the error seems related to my work on DERBY-2193. Regards, -Rick Mike Matrigali wrote: From tinderbox it looks l

Re: how should store get an object based on format id and collation id?

Daniel John Debrunner wrote: Mamta Satoor wrote: I spent some time on points 1(using Monitor to get dvd directly) and 3(optimized allocation, caching some of the work.) which requires us to solve the problem of how to get the InstanceGetter to return the correct DVD for character types. Let

[jira] Updated: (DERBY-2193) [import] ERROR 38000: StringIndexOutOfBoundsException was thrown while evaluating an expression.

[ https://issues.apache.org/jira/browse/DERBY-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-2193: - Attachment: derby-2193-03.diff Commit derby-2193-03.diff at subversion revision 529322. This adju

Re: how should store get an object based on format id and collation id?

Mike asked "Mamta, are you close to an implmentation, maybe you could post a patch so that I could work off of that while discussion continues?" I hope to be able to post something in a days time if everything goes fine. Mamta On 4/16/07, Mike Matrigali <[EMAIL PROTECTED]> wrote: Below as qu

Re: how should store get an object based on format id and collation id?

Daniel John Debrunner wrote: Mamta Satoor wrote: Hi Dan, The problem we are trying to solve is provide a way to Store so that it can call a method (say it's called getInstanceGetterForFormatIDandCollationType) on DVF with format id & collation type and get an InstanceGetter for that comb

[jira] Commented: (DERBY-827) Performance can be improved by re-using language ResultSets across Activation executions.

[ https://issues.apache.org/jira/browse/DERBY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489153 ] Bryan Pendleton commented on DERBY-827: --- It sounds like both the prepared statement and the result set are keepi

Re: how should store get an object based on format id and collation id?

Below as quoted by Mamta are my views on this. I was hoping that compares involving collation chars would not require twice the number of objects being created. Below describes how store uses InstanceGetter currently to optimize allocation of objects. I was hoping to preserve this performance f

Regression Test Report - Daily 528997 - Sun DBTG

[Auto-generated mail] *Daily* 528997/2007-04-15 18:00:11 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0346346 077.62% derbyall F:8,E:073947386 0 592.90% suitesAll sles

Re: is anyone looking at new import/export tinderbox errors that look like they started with checkin for DERBY-2193 or DERBY-2444?

Hi Mike, I will take a look at this. At first blush, the error seems related to my work on DERBY-2193. Regards, -Rick Mike Matrigali wrote: From tinderbox it looks like the new errors showed up in: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/FailReports/528565.html Unfor

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

Issue Subscription Filter: Derby: JIRA issues with patch available (23 issues) Subscriber: derby-dev Key Summary DERBY-2551 Global Xid value garbled in syscs_diag.transaction_table. https://issues.apache.org/jira/browse/DERBY-2551 DERBY-2327 Reduce monitor contention in Lock

is anyone looking at new import/export tinderbox errors that look like they started with checkin for DERBY-2193 or DERBY-2444?

From tinderbox it looks like the new errors showed up in: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/FailReports/528565.html Unfornately this tinderbox run had a number of checkins, so not exactly sure which checkin did it. Both DERBY-2193 and DERBY-2444 seem like they might a

Regression Test Report - tinderbox_trunk16 529212 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 529212/2007-04-16 14:03:13 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0346346 097.09% derbyall F:8,E:073947386 0

[jira] Commented: (DERBY-2544) SecurityPolicyReloadingTest( )junit.framework.AssertionFailedError: Policy file changed. Should not be able to read the property.

[ https://issues.apache.org/jira/browse/DERBY-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489137 ] Rick Hillegas commented on DERBY-2544: -- Re-enabled the SecurityPolicyReloadingTest in the lang suite. Subversion

[jira] Resolved: (DERBY-2495) Create framework for calling locator related stored procedures from client

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

[jira] Created: (DERBY-2552) Specifying a streaming cipher for data encryption causes java.lang.ArithmeticException

Specifying a streaming cipher for data encryption causes java.lang.ArithmeticException -- Key: DERBY-2552 URL: https://issues.apache.org/jira/browse/DERBY-2552 Projec

[jira] Updated: (DERBY-2495) Create framework for calling locator related stored procedures from client

[ https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-2495: --- Derby Info: [Patch Available] > Create framework for calling locator related stored procedure

[jira] Updated: (DERBY-2495) Create framework for calling locator related stored procedures from client

[ https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-2495: --- Attachment: derby-2459-followup.diff This follow-up patch, derby-2495/trunk/derby-2459-follow

[jira] Commented: (DERBY-2544) SecurityPolicyReloadingTest( )junit.framework.AssertionFailedError: Policy file changed. Should not be able to read the property.

[ https://issues.apache.org/jira/browse/DERBY-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489115 ] Rick Hillegas commented on DERBY-2544: -- Thanks for the quick verification, Ole and Dag. I have committed derby-

[jira] Commented: (DERBY-827) Performance can be improved by re-using language ResultSets across Activation executions.

[ https://issues.apache.org/jira/browse/DERBY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489113 ] Dyre Tjeldvoll commented on DERBY-827: -- I've looked some more at the failure in lang/altertable.sql: Dan> I don'

[jira] Commented: (DERBY-2495) Create framework for calling locator related stored procedures from client

[ https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489096 ] Kristian Waagan commented on DERBY-2495: Øystein, see my answers to selected questions below. >> 3) Any reas

[jira] Assigned: (DERBY-1825) Errors 2850A,2850G,28508 are similar - can be combined into a single message.

[ https://issues.apache.org/jira/browse/DERBY-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland reassigned DERBY-1825: Assignee: Jørgen Løland > Errors 2850A,2850G,28508 are similar - can be combined into a sin

[jira] Assigned: (DERBY-1828) Access rule violations should use a SQL state starting with '42' according to the SQL standard.

[ https://issues.apache.org/jira/browse/DERBY-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland reassigned DERBY-1828: Assignee: Jørgen Løland > Access rule violations should use a SQL state starting with '42'

[jira] Commented: (DERBY-2495) Create framework for calling locator related stored procedures from client

[ https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489094 ] Øystein Grøvlen commented on DERBY-2495: Thanks, Kristian for committing this. I will make a follow-up patch

Regression Test Report - tinderbox_trunk16 529163 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 529163/2007-04-16 10:22:38 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0346346 097.06% derbyall F:8,E:073947386 0

[jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489082 ] Bernt M. Johnsen commented on DERBY-2166: - This issue can't be ported to 10.2 or 10.1 since it needs SocketT

[jira] Closed: (DERBY-2550) Types.NULL is not accepted when using setNull on a PreparedStatment

[ https://issues.apache.org/jira/browse/DERBY-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schwanke closed DERBY-2550. - Resolution: Won't Fix Derby Info: (was: [Existing Application Impact, Patch Availabl

[jira] Commented: (DERBY-2550) Types.NULL is not accepted when using setNull on a PreparedStatment

[ https://issues.apache.org/jira/browse/DERBY-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489074 ] Christian Schwanke commented on DERBY-2550: --- Hi, sorry, I missed that one on the mailing list (although I s

Re: Lifetime of Blob/Clob objects, compatibility issues

Daniel John Debrunner wrote: > Oystein Grovlen - Sun Norway wrote: ... >> Some observations I have made: >> >>- In embedded, objects for short LOB values are valid after >> transaction commit, objects for long values are not. The same >> holds after the connection is closed. > seems

[jira] Updated: (DERBY-2495) Create framework for calling locator related stored procedures from client

[ https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2495: --- Derby Info: (was: [Patch Available]) Committed 'blobframework_v2.diff' to trunk with revisi

[jira] Updated: (DERBY-2551) Global Xid value garbled in syscs_diag.transaction_table.

[ https://issues.apache.org/jira/browse/DERBY-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Stroffek updated DERBY-2551: --- Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 10.2.3.0 > Gl

[jira] Commented: (DERBY-2327) Reduce monitor contention in LockSet

[ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489054 ] Knut Anders Hatlen commented on DERBY-2327: --- Thanks a lot for testing the patch, Kristian! It's nice to kno

[jira] Updated: (DERBY-2551) Global Xid value garbled in syscs_diag.transaction_table.

[ https://issues.apache.org/jira/browse/DERBY-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Stroffek updated DERBY-2551: --- Attachment: d2551.diff This simple patch dumps the leading zeros in a hex number in case when

Re: Error while connecting to existing database with create=true

Saurabh Vyas <[EMAIL PROTECTED]> writes: > Hi All, > > I got the following error while I tried to connect to database which > was already existing!!(unlikely to the warning message) > Am I missing anything or can anyone please tell me what went wrong in > this scenario. > Apart when I deleted

[jira] Commented: (DERBY-2550) Types.NULL is not accepted when using setNull on a PreparedStatment

[ https://issues.apache.org/jira/browse/DERBY-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489050 ] Knut Anders Hatlen commented on DERBY-2550: --- Hi Christian, This Spring issue has been discussed earlier. S

Error while connecting to existing database with create=true

Hi All, I got the following error while I tried to connect to database which was already existing!!(unlikely to the warning message) Am I missing anything or can anyone please tell me what went wrong in this scenario. Apart when I deleted the database dir (mydb in my case) and then tried t

[jira] Created: (DERBY-2551) Global Xid value garbled in syscs_diag.transaction_table.

Global Xid value garbled in syscs_diag.transaction_table. - Key: DERBY-2551 URL: https://issues.apache.org/jira/browse/DERBY-2551 Project: Derby Issue Type: Bug Affects Versions: 10

[jira] Commented: (DERBY-2327) Reduce monitor contention in LockSet

[ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489042 ] Kristian Waagan commented on DERBY-2327: I've been using this patch in various loads, and have not seen any p

[jira] Resolved: (DERBY-2478) 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest

[ https://issues.apache.org/jira/browse/DERBY-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-2478. --- Resolution: Fixed Fix Version/s: 10.3.0.0 Committed revision 529162. > 'Inval

[jira] Updated: (DERBY-2478) 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest

[ https://issues.apache.org/jira/browse/DERBY-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2478: -- Component/s: Test Regression Test Failure Derby Info: (was: [Reg

[jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489029 ] Mayuresh Nirhali commented on DERBY-2166: - The fix to the parent issue Derby-1856 was ported to 10.2 and 10.1

[jira] Updated: (DERBY-2478) 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest

[ https://issues.apache.org/jira/browse/DERBY-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2478: -- Attachment: d2478.diff SQLUtilities.getRuntimeStatisticsParser() leaves a ResultSet ope

[jira] Updated: (DERBY-2550) Types.NULL is not accepted when using setNull on a PreparedStatment

[ https://issues.apache.org/jira/browse/DERBY-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schwanke updated DERBY-2550: -- Attachment: SimpleEmbeddedTestCase.java A simple JUnit-Testcase to reproduce the proble

[jira] Created: (DERBY-2550) Types.NULL is not accepted when using setNull on a PreparedStatment

Types.NULL is not accepted when using setNull on a PreparedStatment --- Key: DERBY-2550 URL: https://issues.apache.org/jira/browse/DERBY-2550 Project: Derby Issue Type: Bug

[jira] Assigned: (DERBY-2478) 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest

[ https://issues.apache.org/jira/browse/DERBY-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen reassigned DERBY-2478: - Assignee: Knut Anders Hatlen > 'Invalid transaction state...' in jdbcapi.SetTrans

[jira] Created: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE - Key: DERBY-2549 URL: https://issues.apache.org/jira/browse/DERBY-2549 Project: Derby Issue Ty

[jira] Updated: (DERBY-2540) Restructure code for Blob/Clob length in client to prepare for locator implementation

[ https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-2540: --- Attachment: derby-2540_2.diff Attached patch, derby-2540_2.diff, addresses review comments.

[jira] Commented: (DERBY-2540) Restructure code for Blob/Clob length in client to prepare for locator implementation

[ https://issues.apache.org/jira/browse/DERBY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489031 ] Øystein Grøvlen commented on DERBY-2540: Dag, thanks for the review. I have addressed your comments below, a