[jira] Commented: (DERBY-3593) ErrorCode 30000 when quering a select with 'having' clause and named tables with aliases for selected fields

[ https://issues.apache.org/jira/browse/DERBY-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587490#action_12587490 ] Bryan Pendleton commented on DERBY-3593: Can you provide a complete standalone scri

Re: Helping new people getting started.

Good message! Thank you!

rationale for mandatory RESTRICT on execute revoke?

Hi, For the roles work, when a role grant is revoked, several kinds of privileges conferred by that role grant can be impacted. I was wondering what the rationale is/was for only allowing RESTRICT in the case of revoking an execution privilege (and conversely, for *not* allowing it on other priv

[jira] Updated: (DERBY-3611) ERROR XSDG2: Invalid checksum on Page occurs during mass inserts into two-column bigint PK table

[ https://issues.apache.org/jira/browse/DERBY-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sitsky updated DERBY-3611: Attachment: derby-worker4.log derby-worker3.log Example derby.log file running from

[jira] Created: (DERBY-3611) ERROR XSDG2: Invalid checksum on Page occurs during mass inserts into two-column bigint PK table

ERROR XSDG2: Invalid checksum on Page occurs during mass inserts into two-column bigint PK table Key: DERBY-3611 URL: https://issues.apache.org/jira/browse/DERBY-3611

[jira] Updated: (DERBY-3611) ERROR XSDG2: Invalid checksum on Page occurs during mass inserts into two-column bigint PK table

[ https://issues.apache.org/jira/browse/DERBY-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sitsky updated DERBY-3611: Attachment: derby-worker0.log Example derby.log file running from quad-core machine 0. > ERROR XS

Failure in ServerPropertiesTest on trunk using ibm1.6

Hi, I was wondering if anyone is aware of following failure. This is with trunk at revision 646173. Thanks. java.lang.Exception: DRDA_InvalidReplyTooShort.S:Invalid reply from network server: Insufficient data. at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage

[jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2871: -- Derby Info: [Patch Available] > XATransactionTest gets XaException: Error executing a XAResourc

[jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2871: -- Attachment: derby-2871.v2.diff Attaching a new patch (derby-2971.v2.diff) which re-enables the

Re: Helping new people getting started.

Svein Erik Reknes Løvland wrote: Hi, me and Henrik would like to help the new people if they have any difficulties when starting working on Derby. We'll mainly be available on IRC 8:00-14:00 GMT and try to answer any questions we're able to. Perhaps we can find something that will make starti

Re: [VOTE] V. Narayanan as a committer

Rick Hillegas wrote: Please vote on whether we should make V. Narayanan a Derby committer. +1

Re: [VOTE] Jørgen Løland as a committ er

Rick Hillegas wrote: Please vote on whether we should make Jørgen Løland a Derby committer. The polls close at 5:00 pm San Francisco time on Thursday April 10. +1

Re: [VOTE] V. Narayanan as a committer

+1 Myrna

Re: [VOTE] Jørgen Løland as a committer

+1 Myrna

[jira] Updated: (DERBY-3610) Confusing error message when granting execute privilege

[ https://issues.apache.org/jira/browse/DERBY-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3610: - Component/s: SQL Newcomer > Confusing error message when granting execute privil

Regression Test Report - Daily 645982 - Sun DBTG

[Auto-generated mail] *Daily* 645982/2008-04-08 18:00:59 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0269269 082.50% derbyall F:1,E:098809879 0 1281.59% suitesAll sles

[jira] Updated: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3603: -- Attachment: derbydb.jar Attaching jarred up db for easier access. > 'IN' clause ignores valid

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587239#action_12587239 ] A B commented on DERBY-3603: Thanks for the investigation, Bryan and Thomas! I was hoping to l

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

Issue Subscription Filter: Derby: JIRA issues with patch available (6 issues) Subscriber: derby-dev Key Summary DERBY-2892 Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks https://issues.apache.org/jira/browse/DERBY-

[jira] Updated: (DERBY-3609) Wrong functionality of auto-generated keys support

[ https://issues.apache.org/jira/browse/DERBY-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Alesinskyy updated DERBY-3609: Attachment: TestGeneratedKeys.java Source of above mentioned test programm > Wrong

[jira] Commented: (DERBY-3609) Wrong functionality of auto-generated keys support

[ https://issues.apache.org/jira/browse/DERBY-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587233#action_12587233 ] Oleksandr Alesinskyy commented on DERBY-3609: - Regrettably, after INSERT...SELE

Newcomer issue

Hello, If anyone new wants to get "their hands dirty", DERBY-3601 would be a candicate. It requires understanding a small part of the client driver. A proper patch would go into trunk and the 10.4 branch, maybe also into 10.3. There are also possibilities for more complex follow-up work, for

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12587203#action_12587203 ] Dyre Tjeldvoll commented on DERBY-3431: --- I've been thinking a bit about how best to a

[jira] Commented: (DERBY-2209) derbynet/getCurrentProperties.java fails intermittently

[ https://issues.apache.org/jira/browse/DERBY-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587202#action_12587202 ] Jamie Grinstead commented on DERBY-2209: I also see this on ibm16 occasionally on l

[jira] Issue Comment Edited: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587193#action_12587193 ] thomanie edited comment on DERBY-3603 at 4/9/08 7:05 AM: --- Ran

[jira] Commented: (DERBY-3609) Wrong functionality of auto-generated keys support

[ https://issues.apache.org/jira/browse/DERBY-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587198#action_12587198 ] Bernt M. Johnsen commented on DERBY-3609: - Formally, Derby does not support getGene

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587196#action_12587196 ] Bryan Pendleton commented on DERBY-3603: > the join on either the left or right sid

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587193#action_12587193 ] Thomas Nielsen commented on DERBY-3603: --- Ran the queries through the debugger to see

[jira] Commented: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587191#action_12587191 ] Dyre Tjeldvoll commented on DERBY-2871: --- Thanks for the feedback, Julius. I know that

[jira] Updated: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3347: -- Attachment: d3347-preview.diff Attaching an updated preview patch, still not ready for

Re: Derby crash (urgent)

Hi, I found that the corruption is happening when I startup the server not shutdown, I checked how hibernate creates a connections, for connection pooling; I’m using (C3P0) I disabled that one, and now the derby is working fine without any corruption. I disabled C3P0 (connection pool), and now t

Re: Derby crash (urgent)

I removed c3p0, now its working good. shabz wrote: > > Hi, > > I am also facing same issue. I tried disabling the disk cache also, but > still the same problem. > > > > Bassel_kh wrote: >> >> 1- SYSINFO : >> Java Version : 1.5.0_11-b03 >> os version : 5.1 Windows XP >> For

[jira] Created: (DERBY-3610) Confusing error message when granting execute privilege

Confusing error message when granting execute privilege --- Key: DERBY-3610 URL: https://issues.apache.org/jira/browse/DERBY-3610 Project: Derby Issue Type: Improvement Reporter

[jira] Commented: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587161#action_12587161 ] Julius Stroffek commented on DERBY-2871: Dyre, thanks for working on this. This is

[jira] Issue Comment Edited: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587138#action_12587138 ] thomanie edited comment on DERBY-3603 at 4/9/08 4:05 AM: --- DER

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587138#action_12587138 ] Thomas Nielsen commented on DERBY-3603: --- DERBY-3061 adds a check for "otherPred.isInL

[jira] Updated: (DERBY-2892) Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks

[ https://issues.apache.org/jira/browse/DERBY-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2892: --- Derby Info: [Patch Available, Existing Application Impact, Regression, Release Note Needed]

Re: executeQuery hangs

Hi Radovan! Just a shot in the dark, since I do not know what kind of Windows you run. But if it is Vista, is it possible your installation was upgraded with SP1 last Friday? In that case your firewall-rules probably have changed and you have to grant some permissions one more time. I do not

[jira] Updated: (DERBY-2892) Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks

[ https://issues.apache.org/jira/browse/DERBY-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2892: --- Attachment: derby-2892-2a-alternative_fix_cleanup.diff Forgot to say, but I ran the repro Øys

[jira] Updated: (DERBY-2892) Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks

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

[jira] Commented: (DERBY-2475) invalid checksum

[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587126#action_12587126 ] Shahbaz commented on DERBY-2475: Its Win XP SP2, JVM 1.5 > invalid checksum >

[jira] Reopened: (DERBY-2892) Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks

[ https://issues.apache.org/jira/browse/DERBY-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan reopened DERBY-2892: Reopening to commit alternative fix. I expect there will be two patches, one is ready. The next

[jira] Commented: (DERBY-2475) invalid checksum

[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587123#action_12587123 ] Kristian Waagan commented on DERBY-2475: I note that you say you are frequently fac

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587111#action_12587111 ] Knut Anders Hatlen commented on DERBY-3347: --- The preview patch caused two failure

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587104#action_12587104 ] Knut Anders Hatlen commented on DERBY-3347: --- Another related problem: Before DER

[jira] Created: (DERBY-3609) Wrong functionality of auto-generated keys support

Wrong functionality of auto-generated keys support -- Key: DERBY-3609 URL: https://issues.apache.org/jira/browse/DERBY-3609 Project: Derby Issue Type: Bug Components: JDBC Affects

executeQuery hangs

Hello, I have a java swing application comunicating with Derby 10.1.2.6 DB through JDBC. Since friday one of the application part stoped to work as it cannot get data from database. I found that the last operation is executeQuery invoked on prepared statement. It stops at this point, no another

[jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2871: -- Attachment: derby-2871_NOT_FOR_COMMIT.diff Attaching derby-2871-NOT_FOR_COMMIT.diff where I hav

[jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2871: -- Derby Info: (was: [Patch Available]) > XATransactionTest gets XaException: Error executing a

Re: [VOTE] V. Narayanan as a committer

+1 Rick Hillegas wrote (2008-04-03 10:17:37): > Please vote on whether we should make V. Narayanan a Derby committer. > The polls close at 5:00 pm San Francisco time on Thursday April 10. > > For several years, Narayanan has contributed valuable features and fixes > to Derby, start

Re: [VOTE] Jørgen Lølan d as a committer

+1 Rick Hillegas wrote (2008-04-03 10:03:18): > Please vote on whether we should make Jørgen Løland a Derby committer. > The polls close at 5:00 pm San Francisco time on Thursday April 10. > > Jørgen has contributed significantly to adding replication functionality > to Derby. Alth

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587080#action_12587080 ] Knut Anders Hatlen commented on DERBY-3574: --- Thanks for the patch. From a quick l