[jira] Assigned: (DERBY-449) importing data using SYSCS_UTIL.SYSCS_IMPORT_DATA generates wrong message

[ https://issues.apache.org/jira/browse/DERBY-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Bhaskaran reassigned DERBY-449: Assignee: Abhishek Bhaskaran > importing data using SYSCS_UTIL.SYSCS_IMPORT_DATA gen

[jira] Commented: (DERBY-3037) Language ResultSet.finish() is called even when the ResultSet is going to be re-used.

[ https://issues.apache.org/jira/browse/DERBY-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562831#action_12562831 ] Mamta A. Satoor commented on DERBY-3037: After doing a little more research, it app

[jira] Commented: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby

[ https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562798#action_12562798 ] Dibyendu Majumdar commented on DERBY-3351: -- Hi Dan, Thanks for the input. I agree

[jira] Updated: (DERBY-2142) NullPointerException while using XAConnection/PooledConnection in a heavily contended multithreaded scenario

[ https://issues.apache.org/jira/browse/DERBY-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2142: -- Attachment: derby-2142_stat.txt derby-2142_diff.txt Attached is patch for this

Re: Java doc warning on 10.3

On 1/24/08, Manjula Kutty <[EMAIL PROTECTED]> wrote: > > > > [javadoc] > C:\nightlies\v10_3\src\opensource\java\engine\org\apache\derby\impl\sql\execute\CallStatementResultSet.java:172: > warning - Tag @see: can't find cleanUp in java.sql.ResultSetAny one > recognise this? > -- > Thanks, > Manjula.

Re: Another newbie internals question

Frank Griffin wrote: Kathey Marsden wrote: Frank Griffin wrote: get-go (of course, how you could open JDBC access without actually opening JDBC access is a bit of a conundrum). Any ideas or direction ? You could connect with the embedded driver to do your initial setup before starting net

[jira] Commented: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby

[ https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562769#action_12562769 ] Daniel John Debrunner commented on DERBY-3351: -- Some thinking at a high level

Re: Another newbie internals question

Kathey Marsden wrote: > Frank Griffin wrote: >> get-go (of course, how you could open JDBC access without actually >> opening JDBC access is a bit of a conundrum). >> >> Any ideas or direction ? >> >> > You could connect with the embedded driver to do your initial setup > before starting network

[jira] Commented: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby

[ https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562759#action_12562759 ] Dibyendu Majumdar commented on DERBY-3351: -- Thinking more about it - packages in s

Pluggable Storage Engine Architecture for Derby

Hi All, I have created a task for myself to work on a Pluggable Storage Engine for Derby, similar in concept to MySQL architecture. I would be very grateful for views, comments and insights. The JIRA task is https://issues.apache.org/jira/browse/DERBY-3351. I am at present trying to understa

[jira] Commented: (DERBY-3351) Implement a Pluggable Storage Engine Architecture in Derby

[ https://issues.apache.org/jira/browse/DERBY-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562741#action_12562741 ] Dibyendu Majumdar commented on DERBY-3351: -- Regarding Storage Engine Boundary: Ob

[jira] Assigned: (DERBY-2142) NullPointerException while using XAConnection/PooledConnection in a heavily contended multithreaded scenario

[ https://issues.apache.org/jira/browse/DERBY-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-2142: - Assignee: Kathey Marsden > NullPointerException while using XAConnection/PooledConnection

[jira] Commented: (DERBY-3243) (jdbc net client) exception during normal iteration through "ResultSet" of "select * from t"

[ https://issues.apache.org/jira/browse/DERBY-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562702#action_12562702 ] Kathey Marsden commented on DERBY-3243: --- At the root of this issue is this function i

Re: Expected behavior of WHERE clause referencing expressions in a MaterializedResultSet?

Hi Thomas, It sounds like you're headed in the right direction. One way to test theories like this is to run some experiments in a subversion client which doesn't have your changes. Try creating a query which generates a MaterializedResultSet and then look at the processing to see where (and

Re: Strange NPE in 10.1

Kathey Marsden wrote: Following the possible codepaths through the BrokeredStatement constructor we could get to XAStatementControl.getRealStatement() which might have a null xaconnection. I could try fixing DERBY-2142, if you think it might be related. Seems a little like a shot in the dark s

Re: Strange NPE in 10.1

Daniel John Debrunner wrote: It could be the jit is messing up the line numbers for the NPE, especially if it is in-lining code. Could the NPE be in the BrokeredStatement constructor. Here is the BrokeredStatement constructor: BrokeredStatement(BrokeredStatementControl control, int jdbcLevel)

[jira] Commented: (DERBY-1387) Add JMX extensions to Derby

[ https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562655#action_12562655 ] Rick Hillegas commented on DERBY-1387: -- Hi John, It sounds as though you are on a goo

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3330: -- comments of functional spec/hard upgrade section: It says: During had upgrade existing backing inde

Re: Strange NPE in 10.1

Kathey Marsden wrote: Daniel John Debrunner wrote: Could it be DERBY-2142, which has a valid fix described. Stan and I were looking at 2142, but for it to be that we would expect I think the connection to be null and we have a dereference of it. Here our NPE comes at this line. How can we e

Re: New java doc warnings

Thanks Dag -Manjula On 1/24/08, Dag H. Wanvik <[EMAIL PROTECTED]> wrote: > > Manjula Kutty <[EMAIL PROTECTED]> writes: > > > I'm getting these new jabva doc warnings continuously for 2 days. Can > any > > one please have a look? > > Mea cupla. I'll fix it, thanks! > > Dag > -- Thanks, Manjul

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3330: -- here are some initial comments on the derby-3330v4.diff patch overall: o almost unique, doesn't se

Re: Regression Filter (was Re: Blockers and 10.4)

Ok, I think I've found this one. I subscribed derby-dev to Open Product Regressions. The report should be mailed every Sunday. Regards, -Rick Kathey Marsden wrote: Rick Hillegas wrote: Kathey Marsden wrote: [EMAIL PROTECTED] wrote: Is this query saved as a public filter in Jira? I could not

Re: Strange NPE in 10.1

Daniel John Debrunner wrote: Could it be DERBY-2142, which has a valid fix described. Stan and I were looking at 2142, but for it to be that we would expect I think the connection to be null and we have a dereference of it. Here our NPE comes at this line. How can we even get an NPE with thi

Re: Strange NPE in 10.1

Kathey Marsden wrote: I am working with a user who is getting a NullPointerException in 10.1. Below is the Derby part of the trace: [1/24/08 14:25:59:741 EST] 002b SystemErr R java.lang.NullPointerException org.apache.derby.iapi.jdbc.BrokeredConnection.newBrokeredStatement(BrokeredConnec

Re: [Running] Top-level junit tests - WAS Re: [jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

Vemund Ostgaard wrote: Would it be a good idea for junit-all to just run suites.All directly instead of the different subsuites? This way they would always be in synch. This has the disadvantage that there is less visual feedback when running the junit-all target. Currently at each major sui

Re: Strange NPE in 10.1

Kathey Marsden wrote: I am working with a user who is getting a NullPointerException in 10.1. Below is the Derby part of the trace: The 10.1 version is: 10.1.3.2 - (601970)

[jira] Commented: (DERBY-3221) "java.sql.SQLException: The conglomerate (-5) requested does not exist." from Derby 10.3.1.4 embedded within Eclipse 3.3 and RAD 7.0

[ https://issues.apache.org/jira/browse/DERBY-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562614#action_12562614 ] Tim Halloran commented on DERBY-3221: - Any idea when 10.3.2.2 will be released? I coul

Strange NPE in 10.1

I am working with a user who is getting a NullPointerException in 10.1. Below is the Derby part of the trace: [1/24/08 14:25:59:741 EST] 002b SystemErr R java.lang.NullPointerException org.apache.derby.iapi.jdbc.BrokeredConnection.newBrokeredStatement(BrokeredConnection.java:448) org.apac

[jira] Updated: (DERBY-2683) tools and utilities guide: ij.URLCheck's list of checked attributes is not correct

[ https://issues.apache.org/jira/browse/DERBY-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-2683: - Attachment: rtoolsijpropref38481.html DERBY-2683.diff Thanks for pointing out this proble

[jira] Assigned: (DERBY-2683) tools and utilities guide: ij.URLCheck's list of checked attributes is not correct

[ https://issues.apache.org/jira/browse/DERBY-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase reassigned DERBY-2683: Assignee: Kim Haase > tools and utilities guide: ij.URLCheck's list of checked attributes is not >

Re: Confused about merging and fix versions

Kathey Marsden <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> branch. The fixin fields should be marked as >> >> * 10.1.3.0 - So that it will be in the bug fix release release notes. >> * 10.1.2.x - As shown by sysinfo on the 10.1 branch >> * 10.2.0.x - As shown by sysinfo o

[jira] Commented: (DERBY-3037) Language ResultSet.finish() is called even when the ResultSet is going to be re-used.

[ https://issues.apache.org/jira/browse/DERBY-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562589#action_12562589 ] Mamta A. Satoor commented on DERBY-3037: I spent some time on Dan's suggestion

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Fix Version/s: 10.3.2.2 Adding fix-version 10.3.2.2 since the other DERBY-827 have been merged

[jira] Issue Comment Edited: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562586#action_12562586 ] dyret edited comment on DERBY-3343 at 1/25/08 9:21 AM: Addi

[jira] Updated: (DERBY-3221) "java.sql.SQLException: The conglomerate (-5) requested does not exist." from Derby 10.3.1.4 embedded within Eclipse 3.3 and RAD 7.0

[ https://issues.apache.org/jira/browse/DERBY-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3221: -- Fix Version/s: 10.4.0.0 10.3.2.2 Merged to 10.3 with revision 615273 > "jav

Re: Confused about merging and fix versions

[EMAIL PROTECTED] wrote: branch. The fixin fields should be marked as * 10.1.3.0 - So that it will be in the bug fix release release notes. * 10.1.2.x - As shown by sysinfo on the 10.1 branch * 10.2.0.x - As shown by sysinfo on the trunk" Item 2 and 3 are ok, 10.3.2.2 for 10.3 and 1

[jira] Commented: (DERBY-3301) Incorrect result from query with nested EXIST

[ https://issues.apache.org/jira/browse/DERBY-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562582#action_12562582 ] A B commented on DERBY-3301: Thank you for your continued work on this, Thomas, and for your pa

Confused about merging and fix versions

So I'm getting ready to merge the two regressions I've been working on to the 10.3 branch. Finding http://wiki.apache.org/db-derby/MoveAChangeBetweenBranches was a great help, but I'm slightly confused about the fix-versions. Quoting from the Wiki page above: "Mark the issue resolved only after

[jira] Closed: (DERBY-3297) Document SIGN, SQRT, RAND, RANDOM, COSH, COT, SINH and TANH functions.

[ https://issues.apache.org/jira/browse/DERBY-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen closed DERBY-3297. - Thanks for comitting Dyre. Dan, please reopen it if you feel this is not complete. > Document SIGN,

[jira] Closed: (DERBY-3340) Add debug target to Netbeans 6.0 project file

[ https://issues.apache.org/jira/browse/DERBY-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen closed DERBY-3340. - Thanks for comitting Kristian. Closing. > Add debug target to Netbeans 6.0 project file > --

[jira] Closed: (DERBY-1781) Process handles appear to be leaking in queries using an IN clause during concurrent DB access

[ https://issues.apache.org/jira/browse/DERBY-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen closed DERBY-1781. - Closing in agreement with reporter. Issue fixed in 10.2.1.6. > Process handles appear to be leaking

Regression Test Report - Daily 614927 - Sun DBTG

[Auto-generated mail] *Daily* 614927/2008-01-24 18:01:05 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0273273 072.71% derbyall 01017410174 0 1408.98% suitesAll linN+1

[jira] Commented: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562561#action_12562561 ] Dyre Tjeldvoll commented on DERBY-3343: --- I managed to commit this with a log message

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

Issue Subscription Filter: Derby: JIRA issues with patch available (15 issues) Subscriber: derby-dev Key Summary DERBY-3324 JDBC statement cache implementation https://issues.apache.org/jira/browse/DERBY-3324 DERBY-3205 Replication: Add connection url command options for sta

[jira] Commented: (DERBY-268) Add Support for truncate table

[ https://issues.apache.org/jira/browse/DERBY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562546#action_12562546 ] Daniel John Debrunner commented on DERBY-268: - A more precise statement might be

[jira] Assigned: (DERBY-591) Several builtin functions are incorrectly exposed through the JDBC escaped function syntax {fn }

[ https://issues.apache.org/jira/browse/DERBY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan reassigned DERBY-591: - Assignee: (was: Kristian Waagan) Don't have time for this one now, feel free to grab i

[jira] Closed: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ https://issues.apache.org/jira/browse/DERBY-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-1585. -- Not seen anymore after week 2 when this was fixed > derbylang/procedureInTrigger: not able

[jira] Updated: (DERBY-3324) JDBC statement cache implementation

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

[jira] Closed: (DERBY-2899) Reoccurrence of DERBY-2434: HarnessJavaTest fails on UTF-8 locale.

[ https://issues.apache.org/jira/browse/DERBY-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-2899. -- Since Derby-957 was fixed and this was a duplicate, this one can also be closed. > Reoccur

Re: Request to add to developer list

Hi Deepthi, I have added you to the derby developers list. The following web pages may help you get started: Top level community page: http://db.apache.org/derby/derby_comm.html Page for new developers: http://wiki.apache.org/db-derby/ForNewDevelopers Wiki for Derby contributors: http://wiki

[jira] Closed: (DERBY-2948) Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with '...Connection refused: connect' expecting 'Connection refused'

[ https://issues.apache.org/jira/browse/DERBY-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-2948. -- No longer an issue > Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with

[jira] Closed: (DERBY-3029) Several broken links on Derby web-site

[ https://issues.apache.org/jira/browse/DERBY-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-3029. -- Thanks for working on this! > Several broken links on Derby web-site > ---

[jira] Closed: (DERBY-3030) Several broken links on Derby documentation web-site

[ https://issues.apache.org/jira/browse/DERBY-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-3030. -- Thanks for working on this. I agree that older versions do not need these changes > Sever

Request to add to developer list

Sir Please addd my id deepthidevaki to Derby developers list. Thanks & Regards Deepthi Devaki A R

Re: Use of 'Existing Application Impact'

Hi Dyre, Your understanding agrees with what's documented on the Derby Bug Guidelines page (http://db.apache.org/derby/DerbyBugGuidelines.html): "Existing Application impact: an existing application can be impacted by the solution to this issue." Thanks for volunteering to fix the issues so

[jira] Updated: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3205: - Attachment: stopSlave_v1b.diff stopSlave_v1b.stat Thanks for the quick reply, Nar

Re: [jira] Commented: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable

"Mamta A. Satoor (JIRA)" <[EMAIL PROTECTED]> writes: > [ > https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561582#action_12561582 > ] > > Mamta A. Satoor commented on DERBY-3304: >

[jira] Updated: (DERBY-3301) Incorrect result from query with nested EXIST

[ https://issues.apache.org/jira/browse/DERBY-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-3301: -- Attachment: derby-3301-4.diff Attaching 'derby-3301-4.diff' - comments changed - condition for

[jira] Closed: (DERBY-3156) Convert testing of derby error stream to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vemund Østgaard closed DERBY-3156. -- > Convert testing of derby error stream to JUnit > -- >

[jira] Closed: (DERBY-2279) JDBC3 driver is loaded instead of JDBC4 when running with jdk1.7

[ https://issues.apache.org/jira/browse/DERBY-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vemund Østgaard closed DERBY-2279. -- > JDBC3 driver is loaded instead of JDBC4 when running with jdk1.7 > -

Re: [Running] Top-level junit tests - WAS Re: [jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

Daniel John Debrunner wrote: Vemund Ostgaard wrote: So, I think it would be good to work towards tests being executed in environments that are as similar as possible, and in the same order, etc. when using different mechanisms that are intended to be equivalent. On the other hand having the

Re: Expected behavior of WHERE clause referencing expressions in a MaterializedResultSet?

Thomas Nielsen wrote: Hi, I've run across (yet) a(nother) issue in my work with DERBY-2998. This time about the expected behaviour of a WHERE clause referencing an expression in a MaterializedResultSet. Given the sql query shaped like: SELECT ... FROM ( SELECT , ... FROM ... ) A

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Fix Version/s: 10.4.0.0 > Subsequent calls to PreparedStatement cause > SQLIntegrityConstraint

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Derby Info: [Regression] (was: [Regression, Patch Available]) Committed revision 615203. > Su

Re: [Running] Top-level junit tests - WAS Re: [jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

Daniel John Debrunner wrote: Bryan Pendleton wrote: misconception. Apparently "ant junit-all" runs some tests that are not run by "junit suites.All", and I also think "junit suites.All" runs some tests that are not run by "ant junit-all". I, too, thought these ran the same tests. Do you have

[jira] Commented: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562447#action_12562447 ] Knut Anders Hatlen commented on DERBY-3343: --- Yes, but in that case the problem is

Re: Use of 'Existing Application Impact'

Dag H. Wanvik wrote: [EMAIL PROTECTED] writes: I'm looking through issues that are marked with 'Exiting Application Impact', and there seems to be conflicting interpretations of what this attribute actually means. I have always assumed that it meant: "The fix for this issue, when implemented

[jira] Commented: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562437#action_12562437 ] Dyre Tjeldvoll commented on DERBY-3343: --- But isn't that exactly what would happen wit

[jira] Commented: (DERBY-3320) Database creation and boot should fail if collation=TERRITORY_BASED and the selected locale is not supported

[ https://issues.apache.org/jira/browse/DERBY-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562434#action_12562434 ] Vemund Østgaard commented on DERBY-3320: I am not sure if there is an easier way to

[jira] Commented: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562430#action_12562430 ] Knut Anders Hatlen commented on DERBY-3343: --- Thanks Dyre, +1 to commit. > the as

[jira] Commented: (DERBY-268) Add Support for truncate table

[ https://issues.apache.org/jira/browse/DERBY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562428#action_12562428 ] Knut Anders Hatlen commented on DERBY-268: -- Truncate table is implemented, but only

[jira] Commented: (DERBY-3301) Incorrect result from query with nested EXIST

[ https://issues.apache.org/jira/browse/DERBY-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562427#action_12562427 ] Thomas Nielsen commented on DERBY-3301: --- Thanks for the input Army. Ad 1) I agree, t

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Attachment: d3343.v3.diff Attaching another patch (v3) which fixes the javadoc typo and removes

[jira] Commented: (DERBY-3352) truncateTable crashed, Caused by: java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/DERBY-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562420#action_12562420 ] Knut Anders Hatlen commented on DERBY-3352: --- I found this comment in AlterTableNo

[jira] Commented: (DERBY-3352) truncateTable crashed, Caused by: java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/DERBY-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562418#action_12562418 ] Knut Anders Hatlen commented on DERBY-3352: --- Thanks, I also see the NPE when I ru

[jira] Commented: (DERBY-3352) truncateTable crashed, Caused by: java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/DERBY-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562417#action_12562417 ] QingpingXu commented on DERBY-3352: --- i download the source code from svn and compile it a

[jira] Updated: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3205: --- Attachment: Socket_Close_Fix_v1.stat Socket_Close_Fix_v1.diff You are right in your o

[jira] Commented: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562396#action_12562396 ] Knut Anders Hatlen commented on DERBY-3343: --- Looks good to me. Two nits: 1) Ther

[jira] Commented: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562392#action_12562392 ] Jørgen Løland commented on DERBY-3205: -- stopSlave is almost ready now, but I can't see

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Derby Info: [Patch Available, Regression] (was: [Regression]) > Subsequent calls to PreparedSt

[jira] Updated: (DERBY-3343) Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is "Generated always"

[ https://issues.apache.org/jira/browse/DERBY-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3343: -- Attachment: d3343.v2.diff Attaching new patch (v2) which fixes the incorrect comment, and adds