unsubscribe

[jira] Commented: (DERBY-4062) Method override missing from DataValueFactory interface

[ https://issues.apache.org/jira/browse/DERBY-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674567#action_12674567 ] Knut Anders Hatlen commented on DERBY-4062: --- I find this change confusing too.

[jira] Commented: (DERBY-4062) Method override missing from DataValueFactory interface

[ https://issues.apache.org/jira/browse/DERBY-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674568#action_12674568 ] Kristian Waagan commented on DERBY-4062: I guess the DataValueFactory interface

[jira] Commented: (DERBY-4062) Method override missing from DataValueFactory interface

[ https://issues.apache.org/jira/browse/DERBY-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674580#action_12674580 ] Knut Anders Hatlen commented on DERBY-4062: --- The methods that have different

Does Derby supports Not Null constraint on Normal Column

We are using Derby 10.1.3.2 and declared a column with Not null constraint but what we are noticing that it still accept Null value in that column. So i was wondering whether its a known issue / limitation. Regards, Partha Sarthi Technical Consultant – BPM | IBM India Software Lab IBM Software

[jira] Resolved: (DERBY-4027) An attempt was made to access an out of range slot on a page

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

[jira] Created: (DERBY-4063) Constraint causes wrong query result when using exists

Constraint causes wrong query result when using exists -- Key: DERBY-4063 URL: https://issues.apache.org/jira/browse/DERBY-4063 Project: Derby Issue Type: Bug Components: SQL

[jira] Created: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

interaction between derby and jdk 1.5.0_17 causes core dump --- Key: DERBY-4064 URL: https://issues.apache.org/jira/browse/DERBY-4064 Project: Derby Issue Type: Bug Affects

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Attachment: hs_err_pid156.log core dump on winXP-jboss4.0.5 interaction between derby and jdk 1.5.0_17

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Attachment: hs_err_pid600.log winXP-jboss5.0.0 interaction between derby and jdk 1.5.0_17 causes core

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Environment: windows XP SP3, jdk 1.5.0_17, jboss 4.0.5-GA windows XP SP3, jdk 1.5.0_17, jboss

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Attachment: hs_err_pid30771.log lin2.6.18-128.el5 - jboss5.0.0-GA interaction between derby and jdk

Re: Bumping the fourth digit

Andrew McIntyre wrote: On Tue, Feb 17, 2009 at 1:00 PM, Rick Hillegas richard.hille...@sun.com wrote: I prefer the first approach. I would like to summarize its features: a) Any committer can bump the 4th digit of the release id without initiating a community discussion. This lets people

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Environment: windows XP SP3, jdk 1.5.0_17, jboss 4.0.5-GA windows Server 2003 SP2, jdk 1.5.0_17, jboss

[jira] Commented: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674630#action_12674630 ] Bryan Pendleton commented on DERBY-4064: I think you need to pursue this with your

[jira] Updated: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump

[ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] primasol updated DERBY-4064: Attachment: hs_err_pid5340_withDerby10.2.1.6.log winServer2003sp2 - jboss405-GA - derby 10.2.1.6

Re: Does Derby supports Not Null constraint on Normal Column

Partha Sarthi wrote: We are using Derby 10.1.3.2 and declared a column with Not null constraint but what we are noticing that it still accept Null value in that column. Can you provide a test script or test program which demonstrates this? thanks, bryan

[jira] Updated: (DERBY-4062) Remove single-argument getDataValue overrides from DataValueFactory interface

[ https://issues.apache.org/jira/browse/DERBY-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-4062: --- Description: [ Issue title edited to reflect the discussion about how to clarify the

Regression Test Report - tinderbox_10.4_16 745492 - Sun Database Engineering

[Auto-generated mail] *tinderbox_10.4_16* 745492/2009-02-18 13:17:32 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 022 085.00%

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

Issue Subscription Filter: Derby: JIRA issues with patch available (9 issues) Subscriber: derby-dev Key Summary DERBY-2201 Calling functions that return Blob/Clob does not work. https://issues.apache.org/jira/browse/DERBY-2201 DERBY-2389 DOCS - Move Derby system and

[jira] Commented: (DERBY-646) In-memory backend storage support

[ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674692#action_12674692 ] Kathey Marsden commented on DERBY-646: -- As Kristian mentioned, you can disable error

Regression Test Report - Daily 745152 - Sun DBTG

[Auto-generated mail] *Daily* 745152/2009-02-17 18:00:19 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin F:1,E:01091610915 0 1881.59% suitesAll 01313 0 .% jdbcapiAutoLoad 0

Re: Bumping the fourth digit

Rick Hillegas richard.hille...@sun.com writes: Hi Andrew, Can you help me understand why we need to add 2 new versions to JIRA and not just 1? One of the versions means the next official release on this branch. I understand what to do with that release id: I put it in the fixed in field.

[jira] Updated: (DERBY-4040) SQLChar.getLength returns wrong length for some data values

[ https://issues.apache.org/jira/browse/DERBY-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-4040: --- Attachment: derby-4040-2a-backport.diff Attached the diff for the backport,

Re: Bumping the fourth digit

Knut Anders Hatlen wrote: Hi Rick, My understanding is actually the opposite: 10.3.4.0 refers to the next official release and should not be used for the fixed in field for the fixes that we have committed. (At one point we may have used it to say it is my intention to fix this bug for that

Re: Bumping the fourth digit

On Wed, Feb 18, 2009 at 5:53 AM, Rick Hillegas richard.hille...@sun.com wrote: Hi Andrew, Can you help me understand why we need to add 2 new versions to JIRA and not just 1? One of the versions means the next official release on this branch. I understand what to do with that release id: I

Re: Bumping the fourth digit

Andrew McIntyre wrote: On Wed, Feb 18, 2009 at 5:53 AM, Rick Hillegas richard.hille...@sun.com wrote: Hi Andrew, Can you help me understand why we need to add 2 new versions to JIRA and not just 1? One of the versions means the next official release on this branch. I understand what to do

Regression Test Report - tinderbox_10.4_16 745577 - Sun Database Engineering

[Auto-generated mail] *tinderbox_10.4_16* 745577/2009-02-18 18:17:36 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 022 085.00%

[jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674816#action_12674816 ] Kim Haase commented on DERBY-2389: -- Committed patch DERBY-2389-phase2.diff to

[jira] Commented: (DERBY-4063) Constraint causes wrong query result when using exists

[ https://issues.apache.org/jira/browse/DERBY-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674882#action_12674882 ] Bryan Pendleton commented on DERBY-4063: This seems like an interesting problem. It